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 Tracks" operation, it retrieves the list of tracks contained in a specified playlist by its ID. This is useful when you want to programmatically fetch all songs from a particular playlist for further processing, analysis, or integration into other workflows.
Common scenarios:
- Aggregating tracks from user-curated playlists for reporting or analytics.
- Synchronizing playlist contents with another music service or database.
- Creating custom notifications or recommendations based on playlist tracks.
Example:
You have a playlist ID and want to get all tracks within that playlist to display them in a dashboard or use them as input for another automation step.
Properties
| Name | Meaning |
|---|---|
| Resource ID | The unique identifier of the playlist whose tracks you want to retrieve (string). |
| Return All | Whether to return all tracks in the playlist or limit the number of results (boolean). |
| Offset | The starting position in the list of tracks to begin returning results (number, ≥0). |
| Limit | Maximum number of tracks to return if not returning all (number, ≥1). |
Output
The node outputs an array of JSON objects representing the tracks in the specified playlist. Each object contains detailed information about a track, such as title, artist, album, duration, and other metadata provided by the Deezer API.
If the user chooses to return all tracks, the node handles pagination internally to collect all available tracks.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential for Deezer to authenticate requests.
- Uses the Deezer public API endpoint
https://api.deezer.com. - The node depends on helper functions to obtain the access token and make HTTP requests to Deezer.
- No additional environment variables are required beyond the configured Deezer OAuth2 credentials.
Troubleshooting
- Invalid or expired credentials: If the OAuth2 token is invalid or expired, the node will fail to authenticate. Re-authenticate the Deezer credentials in n8n.
- Playlist ID not found: Providing an incorrect or non-existent playlist ID will result in an error from the Deezer API. Verify the playlist ID is correct.
- Rate limiting: Deezer API may impose rate limits; excessive requests might cause temporary failures.
- Pagination issues: If "Return All" is false but the limit is set too low, you may receive incomplete track lists. Adjust the limit or enable "Return All" to fetch all tracks.
- Network errors: Ensure n8n has internet access and can reach
api.deezer.com.