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 data related to users, specifically here focusing on the "Get Recent Tracks" operation for the User resource. It fetches tracks that a user has recently listened to on Deezer. This is useful for scenarios such as building personalized music dashboards, analytics on listening habits, or syncing recent activity with other services.

For example, you could use this node to:

  • Display a user's most recently played songs in a custom app.
  • Analyze trends in a user's listening behavior over time.
  • Trigger workflows based on new tracks a user listens to.

Properties

Name Meaning
Return My User Boolean option to choose whether to return data for the logged-in user (true) or a specific user (false).
User ID The Deezer user ID to fetch recent tracks for (required if "Return My User" is false).
Return All Whether to return all available recent tracks or limit the number of results returned.
Offset The starting index offset for pagination when not returning all results.
Limit Maximum number of recent tracks to return when not returning all results.

Output

The output is a JSON array where each item represents a track recently listened to by the specified user. Each track object contains metadata about the track as provided by the Deezer API, such as track title, artist, album, duration, and other relevant details.

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 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 the Deezer OAuth2 credentials are correctly configured and refreshed.
    • Incorrect User ID: If specifying a user ID manually, verify it exists and is accessible.
    • API rate limits: Deezer may throttle requests; consider using pagination (offset and limit) or enabling Return All carefully.

  • Error messages:

    • Errors from the Deezer API will be returned in the output JSON under an error field if "Continue On Fail" is enabled.
    • Authentication errors typically indicate issues with the OAuth2 token.
    • Validation errors occur if required parameters like User ID are missing when needed.

Links and References

Discussion