Actions43
- Album Actions
- Artist Actions
- Chart Actions
- Playlist Actions
- Podcast Actions
- Track Actions
- User Actions
Overview
This node integrates with the Deezer API to retrieve music chart data, specifically allowing users to get lists of popular albums, artists, playlists, podcasts, or tracks from Deezer's charts. The "Get All" operation under the "Chart" resource fetches a paginated list of chart items, which is useful for applications that want to display trending or top-ranked music content.
Common scenarios include:
- Displaying current top tracks or albums in a music app.
- Aggregating popular playlists or podcasts for recommendation engines.
- Building dashboards or reports based on trending music data.
Example: A user wants to show the top 50 tracks currently trending on Deezer. They can configure this node to fetch the chart tracks with pagination options to control how many results are returned and from which offset.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available results or limit the number of results returned. |
| Offset | The starting position (index) of the first item to retrieve in the chart list. |
| Limit | The maximum number of results to return when not returning all. |
Output
The node outputs an array of JSON objects representing chart items corresponding to the selected type (albums, artists, playlists, podcasts, or tracks). Each item contains metadata as provided by the Deezer API, such as IDs, titles, artist names, rankings, and other relevant details depending on the chart category.
If binary data were involved (e.g., album cover images), it would be included in the binary output field, but this node focuses on JSON data only.
Dependencies
- Requires an OAuth2 API credential for Deezer to authenticate requests.
- Uses the Deezer public API endpoint
https://api.deezer.com. - Relies on internal helper functions for token management and HTTP requests.
- No additional external services beyond Deezer API are needed.
Troubleshooting
- Authentication errors: If the OAuth2 token is invalid or expired, the node will fail to fetch data. Ensure the Deezer API credentials are correctly configured and refreshed.
- Rate limiting: Deezer API may impose rate limits; if exceeded, requests might fail or return errors. Implement retry logic or reduce request frequency.
- Invalid parameters: Providing negative offsets or zero/negative limits will cause errors. Use valid non-negative integers for these properties.
- Empty results: If the offset exceeds the total number of chart items, the node will return an empty array. Adjust offset accordingly.
Links and References
- Deezer API Documentation: https://developers.deezer.com/api/chart
- Deezer OAuth2 Authentication Guide: https://developers.deezer.com/api/oauth
- n8n Documentation on Credentials: https://docs.n8n.io/credentials/overview/