Deezer icon

Deezer

Access public song data via the Deezer API
Join our community

Actions43

Overview

This node integrates with the Deezer API to manage music playlists and tracks. Specifically, for the Playlist - Remove a Track operation, it allows users to remove a specific track from a given playlist by providing the playlist ID and the track ID. This is useful in scenarios where you want to programmatically curate or update playlists by removing unwanted tracks.

Practical examples include:

  • Automatically cleaning up playlists by removing tracks that no longer fit a theme.
  • Managing collaborative playlists by removing duplicate or inappropriate tracks.
  • Integrating with other workflows that trigger track removals based on user preferences or external events.

Properties

Name Meaning
Resource ID The unique identifier of the playlist from which a track will be removed.
Track ID The unique identifier of the track to be removed from the specified playlist.
Return All Whether to return all results or limit the number of returned items (true/false).
Offset The starting position (offset) for fetching results when not returning all (integer ≥ 0).
Limit The maximum number of results to return when not returning all (integer ≥ 1).

Output

The node outputs JSON data representing the result of the track removal operation. Typically, this includes confirmation of the removal or any relevant metadata returned by the Deezer API about the updated playlist state.

If binary data were involved (e.g., audio files), it would be summarized here, but this operation deals only with JSON responses related to playlist management.

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 provided credentials before making API calls.
  • No additional environment variables are required beyond the configured Deezer OAuth2 credentials.

Troubleshooting

  • Common issues:

    • Invalid or expired OAuth2 token: Ensure the Deezer OAuth2 credentials are valid and refreshed.
    • Incorrect playlist or track IDs: Verify that the provided IDs exist and belong to the authenticated user or are publicly accessible.
    • API rate limits: Deezer may throttle requests; consider adding delays or handling rate limit errors gracefully.

  • Error messages:

    • Errors returned from the Deezer API will be included in the output if "Continue On Fail" is enabled.
    • Common error messages might include "Invalid access token," "Playlist not found," or "Track not found."
    • To resolve, check credentials, verify resource IDs, and ensure proper permissions.

Links and References

Discussion