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 user-related music data. Specifically, for the "User" resource and the "Get Flow" operation, it fetches the personalized music flow (a stream of recommended tracks) for a specified user or the authenticated user. This is useful in scenarios where you want to access a user's current music recommendations or listening flow from Deezer.

Practical examples:

  • Automatically fetching your own Deezer music flow to create a playlist or analyze your current music taste.
  • Retrieving another user's flow (if authorized) to see their music recommendations or share them.

Properties

Name Meaning
Return My User Boolean option to choose whether to return the logged-in user's flow (true) or a specific user's flow (false).
User ID The Deezer user ID to get the flow for, required if "Return My User" is set to false.
Return All Whether to return all results or limit the number of returned items.
Offset The offset index of the first object to retrieve (used when not returning all).
Limit Maximum number of results to return (used when not returning all).

Output

The output is a JSON array representing the user's music flow data retrieved from Deezer. Each item corresponds to a track or recommendation in the flow. The structure matches Deezer's API response for user flow, typically including track metadata such as title, artist, album, duration, and other relevant details.

No binary data output is indicated for this operation.

Dependencies

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

Troubleshooting

  • Common issues:

    • Invalid or expired OAuth2 token may cause authentication failures.
    • Requesting another user's flow without proper permissions might result in authorization errors.
    • Incorrect user ID format or empty user ID when "Return My User" is false will cause request failures.

  • Error messages:

    • Errors from the Deezer API will be returned in the output JSON under an error field if "Continue On Fail" is enabled.
    • Common error messages include authentication errors ("Invalid access token"), permission denied, or resource not found.

  • Resolutions:

    • Ensure the OAuth2 credentials are valid and refreshed.
    • Verify that the user ID is correct and accessible.
    • Enable "Continue On Fail" to handle errors gracefully during batch executions.

Links and References

Discussion