Deezer icon

Deezer

Access public song data via the Deezer API

Overview

This node integrates with the Deezer API to manage playlists, specifically allowing users to add tracks to an existing playlist by specifying both the playlist and track IDs. It is useful in scenarios where you want to programmatically update a playlist with new songs, such as automating music curation or syncing playlists from other sources.

For example, you could use this node to add a favorite track to a specific playlist whenever a certain event occurs, like adding a newly discovered song to your "Workout Mix" playlist automatically.

Properties

Name Meaning
Resource ID The unique identifier of the playlist to which tracks will be added.
Track ID The unique identifier of the track to add to the specified playlist.
Return All Whether to return all results or limit the number of returned items.
Offset The starting position (offset) for fetching results when not returning all.
Limit The maximum number of results to return when not returning all.

Output

The node outputs JSON data representing the result of the add tracks operation on the playlist. This typically includes confirmation details about the updated playlist or the status of the addition request. The output is structured as an array of JSON objects, each corresponding to an input item processed.

No binary data output is involved in this operation.

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 within n8n to obtain a valid access token.

Troubleshooting

  • Common issues:

    • Invalid or expired OAuth2 token may cause authentication failures.
    • Incorrect playlist or track IDs will result in errors from the Deezer API.
    • Network connectivity issues can prevent successful API calls.
  • Error messages:

    • Errors related to authorization usually indicate problems with the OAuth2 credentials; re-authenticate or refresh tokens as needed.
    • "Track or Playlist not found" errors suggest invalid IDs; verify that the provided IDs exist and are correct.
    • Rate limiting or API quota exceeded errors require waiting or adjusting usage patterns.

Links and References

Discussion