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 a user's favorite tracks. It can fetch either the favorite tracks of the logged-in user or those of a specific user by their user ID. This is useful for scenarios where you want to analyze, display, or process a user's preferred music tracks from Deezer, such as building personalized playlists, generating music recommendations, or integrating user preferences into other applications.

For example, a music app could use this node to show a logged-in user's favorite tracks or to compare favorite tracks between different users.

Properties

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

Output

The output is a JSON array where each item represents a favorite track object retrieved from Deezer. Each track object contains detailed information about the track, such as its title, artist, album, duration, and other metadata provided by the Deezer API.

If binary data were involved (e.g., audio files), it would be summarized here, but this node only returns JSON metadata about tracks.

Dependencies

  • Requires an OAuth2 API credential for Deezer to authenticate requests.
  • Uses the Deezer public API endpoint: https://api.deezer.com.
  • The node internally obtains an access token using the provided credentials before making API calls.
  • No additional environment variables are required beyond the OAuth2 credential setup in n8n.

Troubleshooting

  • Common issues:

    • Invalid or expired OAuth2 token: Ensure the Deezer OAuth2 credentials are correctly configured and refreshed.
    • Incorrect user ID: If specifying a user ID, verify that it exists and is accessible.
    • Rate limiting by Deezer API: If many requests are made rapidly, the API may throttle responses.

  • Error messages:

    • Errors returned from the Deezer API will be included in the output if "Continue On Fail" is enabled.
    • Common error messages include authentication failures or invalid parameters; resolving these usually involves checking credentials and input values.

Links and References

Discussion