Deezer icon

Deezer

Access public song data via the Deezer API
Join our community

Actions43

Overview

This node integrates with the Deezer API to retrieve a user's favorite artists. It allows you to fetch either the currently authenticated user's favorite artists or those of a specific user by their user ID. This is useful for music apps, analytics, or personalized recommendations where you want to access and process users' favorite artist data from Deezer.

Practical examples:

  • Fetch your own favorite artists to create a personalized playlist.
  • Retrieve another user's favorite artists for social sharing or comparison.
  • Aggregate favorite artists data for multiple users in a marketing or research workflow.

Properties

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

Output

The node outputs an array of JSON objects representing favorite artists. Each object contains details about an artist as provided by the Deezer API, such as artist name, ID, and other metadata.

If binary data were involved (e.g., images), it would be summarized here, but this operation returns only JSON data related to artists.

Dependencies

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

Troubleshooting

  • Authentication errors: Ensure the OAuth2 credential is valid and has the necessary permissions to access user data.
  • Invalid User ID: If specifying a user ID, verify that the ID exists and is accessible.
  • Rate limiting: Deezer API may limit requests; consider handling rate limits or using pagination via offset and limit.
  • Empty results: If no favorite artists are returned, check if the user actually has favorites or if the correct user ID is used.
  • Continue on Fail: The node supports continuing execution on failure per item, which helps in batch processing scenarios.

Links and References

Discussion