Deezer icon

Deezer

Access public song data via the Deezer API
Join our community

Actions43

Overview

This node integrates with the Deezer API to manage playlists, specifically allowing users to create new playlists on their Deezer account. It is useful for automating playlist creation workflows, such as generating personalized playlists based on user preferences or external data sources.

For example, a user could automate the creation of a "Workout Mix" playlist by feeding in a list of tracks and then creating the playlist via this node. This saves manual effort and enables dynamic playlist management within an automation workflow.

Properties

Name Meaning
Resource ID The unique identifier of the resource (album, artist, playlist, track, podcast). Required for most operations except search.
Name The name of the playlist to create. Required when creating a playlist.
Return All Whether to return all results or limit the number of returned items.
Offset The starting index from which to return results (used when not returning all).
Limit The maximum number of results to return (used when not returning all).

Output

The node outputs JSON data representing the result of the playlist creation operation. This typically includes details about the newly created playlist such as its ID, name, and other metadata returned by the Deezer API.

If the operation fails, the output will contain an error message describing the issue.

No binary data output is produced by this node.

Dependencies

  • Requires an OAuth2 API credential for Deezer to authenticate requests.
  • Uses the Deezer public API endpoint https://api.deezer.com.
  • Requires proper configuration of the OAuth2 credentials in n8n to obtain access tokens.

Troubleshooting

  • Common issues:

    • Invalid or expired OAuth2 token: Ensure that the OAuth2 credentials are correctly set up and refreshed.
    • Missing required parameters: The "Name" property must be provided when creating a playlist.
    • API rate limits: Deezer may limit the number of requests; handle errors accordingly.

  • Error messages:

    • Errors returned from the Deezer API will be included in the output JSON under an error field.
    • If the node is configured to continue on failure, it will output the error message per item instead of stopping execution.

Links and References

Discussion