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 podcast episodes. Specifically, the "Get Episodes" operation fetches a list of episodes for a specified podcast by its ID. This is useful when you want to automate workflows that involve accessing podcast content metadata, such as aggregating episode information, creating podcast catalogs, or triggering actions based on new episodes.

Practical examples:

  • Automatically fetching all episodes of a podcast to update a database or CMS.
  • Retrieving a limited number of recent episodes for display in an app or website.
  • Using episode data to trigger notifications or further processing in an automation workflow.

Properties

Name Meaning
Resource ID The unique identifier of the podcast from which to get episodes (e.g., "1234567").
Return All Whether to return all available episodes or limit the number of results returned.
Offset The starting position in the list of episodes to begin returning results (zero-based).
Limit The maximum number of episodes to return if not returning all. Minimum value is 1.

Output

The node outputs JSON data representing the podcast episodes retrieved from Deezer. Each item in the output array corresponds to one episode and includes metadata fields as provided by the Deezer API, such as episode title, description, release date, 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 episodes.

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 credentials will cause authentication failures.
    • Providing an incorrect or non-existent podcast Resource ID will result in errors or empty results.
    • Requesting too many episodes without setting "Return All" may lead to incomplete data due to limits.

  • Error messages:

    • Authentication errors typically indicate problems with the OAuth2 token; re-authenticate or refresh credentials.
    • "Resource not found" or similar errors suggest the podcast ID does not exist or is inaccessible.
    • Rate limiting errors from Deezer API require waiting before retrying or reducing request frequency.

Links and References

Discussion