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 data, specifically focusing on fetching followers of a user. It allows you to either get the followers of the currently authenticated (logged-in) user or any other specified user by their User ID. This is useful in scenarios where you want to analyze social engagement, build follower lists, or integrate Deezer user data into workflows.

Practical examples:

  • Fetch all followers of your own Deezer account to analyze your audience.
  • Retrieve followers of a specific artist or user to understand their fan base.
  • Use follower data to trigger marketing campaigns or notifications.

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 unique identifier of the user whose followers you want to retrieve. Required if "Return My User" is false.
Return All Whether to return all followers or limit the number of results returned.
Offset The starting position (offset) in the list of followers from which to begin returning results. Used only if "Return All" is false.
Limit Maximum number of follower results to return. Used only if "Return All" is false.

Output

The node outputs an array of JSON objects representing the followers of the specified user. Each object corresponds to a follower and contains their user details as provided by the Deezer API.

If binary data were involved (not in this operation), it would be summarized accordingly, but here the output is purely JSON-based user data.

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 that the Deezer OAuth2 credentials are correctly configured and refreshed.
    • Incorrect User ID: If "Return My User" is false, providing an invalid or non-existent User ID will result in errors or empty results.
    • API rate limits: Deezer may impose rate limits; excessive requests might cause temporary failures.

  • Error messages:

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

  • Resolution tips:

    • Verify OAuth2 credentials and re-authenticate if necessary.
    • Double-check User ID values.
    • Use pagination parameters ("Offset" and "Limit") to manage large datasets and avoid timeouts.

Links and References

Discussion