Actions43
- Album Actions
- Artist Actions
- Chart Actions
- Playlist Actions
- Podcast Actions
- Track Actions
- User Actions
Overview
This node integrates with the Deezer API to access public music data. Specifically, for the Playlist resource with the "Get Radio" operation, it fetches a list of recommended tracks based on a given playlist ID. This is useful when you want to generate personalized or related music recommendations derived from an existing playlist.
Practical examples include:
- Creating dynamic radio stations or playlists that adapt to user preferences.
- Building music discovery features by suggesting tracks similar to those in a user's playlist.
- Enhancing music apps or workflows with automated playlist expansions.
Properties
| Name | Meaning |
|---|---|
| Resource ID | The unique identifier of the playlist for which to get recommendation tracks (playlist ID). |
| Return All | Whether to return all available recommendation tracks or limit the number of results. |
| Offset | The starting position in the result set from which to return tracks (used if not returning all). |
| Limit | Maximum number of recommendation tracks to return (used if not returning all). |
Output
The node outputs JSON data representing the recommended tracks related to the specified playlist. Each item in the output array corresponds to a track object containing details such as track title, artist, album, duration, and other metadata provided by the Deezer API.
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. - Requires n8n environment configured with the appropriate Deezer OAuth2 credentials.
- Utilizes helper functions for token management and HTTP requests bundled within the node's dependencies.
Troubleshooting
Common issues:
- Invalid or expired OAuth2 token: Ensure the Deezer OAuth2 credentials are correctly configured and refreshed.
- Incorrect playlist ID: Verify the playlist ID exists and is accessible publicly or by the authenticated user.
- Rate limiting by Deezer API: If many requests are made rapidly, the API may throttle responses; implement delays or reduce request frequency.
Error messages:
"error": "Invalid access token": Reauthenticate or refresh the OAuth2 token."error": "Playlist not found": Check the playlist ID parameter for correctness.- Network or timeout errors: Confirm network connectivity and Deezer API availability.
Links and References
- Deezer API Documentation: https://developers.deezer.com/api
- Deezer Playlist Radio Endpoint: https://developers.deezer.com/api/playlist/radio
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/