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 albums. It allows you to fetch either the favorite albums of the currently authenticated 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 albums from Deezer.

Practical examples include:

  • Building personalized music dashboards showing a user's favorite albums.
  • Aggregating favorite album data for social or music recommendation apps.
  • Automating workflows that react to changes in a user's favorite albums.

Properties

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

Output

The node outputs an array of JSON objects representing the favorite albums retrieved from Deezer. Each object corresponds to one album and contains details as provided by the Deezer API, such as album title, artist, cover image URLs, release date, and other metadata.

If the node supports binary data output (not explicitly shown here), it would typically represent album cover images or related media files. However, this node primarily returns JSON data about albums.

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 via the configured OAuth2 credentials.
  • No additional environment variables are required beyond the OAuth2 credential setup.

Troubleshooting

  • Common issues:

    • Invalid or expired OAuth2 token: Ensure your Deezer OAuth2 credentials are correctly configured and refreshed.
    • Incorrect User ID: If specifying a user ID, verify it exists and is accessible.
    • API rate limits: Deezer may throttle requests; consider using pagination with offset and limit.

  • Error messages:

    • Errors returned from the Deezer API will be included in the output if "Continue On Fail" is enabled.
    • Common error messages might include authentication failures or resource not found errors.

  • Resolution tips:

    • Double-check OAuth2 credentials and re-authenticate if necessary.
    • Validate user IDs before running the node.
    • Use the "Return All" property carefully to avoid large data requests that may time out.

Links and References

Discussion