Deezer icon

Deezer

Access public song data via the Deezer API
Join our community

Actions43

Overview

This node interacts with the Deezer API to retrieve user-related playlist data. Specifically, for the "User" resource and the "Get Playlists" operation, it fetches playlists associated with a user account. It supports fetching playlists of either the logged-in user or any specific user by their user ID.

Common scenarios include:

  • Retrieving all playlists created or followed by a user.
  • Displaying a user's playlists in an application or workflow.
  • Analyzing or processing playlists for music recommendation or curation.

Practical example:

  • A music app workflow that automatically fetches the logged-in user's playlists to display or sync them elsewhere.
  • A marketing tool that gathers public playlists from a specific user to analyze trends or popular tracks.

Properties

Name Meaning
Return My User Boolean option to choose whether to return playlists of the logged-in user (true) or a specific user (false).
User ID The unique identifier of the user whose playlists you want to retrieve (required if "Return My User" is false).
Return All Whether to return all playlists or limit the number of results returned.
Offset The starting index offset for the playlists to retrieve (used when not returning all).
Limit Maximum number of playlists to return (used when not returning all).

Output

The output is a JSON array where each item represents a playlist object retrieved from Deezer. Each playlist object contains details such as playlist ID, title, description, number of tracks, creator information, and other metadata as provided by the Deezer API.

If binary data were involved (e.g., album art images), it would be included separately, but this operation focuses on JSON playlist data only.

Dependencies

  • Requires an OAuth2 API credential for Deezer to authenticate requests.
  • Uses the Deezer API endpoint at https://api.deezer.com.
  • Requires n8n environment configured with the appropriate Deezer OAuth2 credentials.

Troubleshooting

  • Authentication errors: If the OAuth2 token is invalid or expired, the node will fail. Refresh or reauthorize the Deezer credentials.
  • Invalid User ID: Providing an incorrect or non-existent user ID will result in an error or empty results.
  • Rate limiting: Deezer API may limit requests; if too many requests are made in a short time, expect errors or throttling.
  • Empty results: If the user has no playlists or the offset/limit parameters exclude all results, the output will be empty.
  • Continue on Fail: If enabled, the node will continue processing other items even if one fails, returning error messages in the output JSON.

Links and References

Discussion