FlowRunner
PricingContact
Theme
Start Free

Deezer

Media & Video

Deezer is a music streaming catalog with albums, artists, tracks, playlists, charts, radios, and podcasts. Agents search the catalog, read charts and editorial picks, and manage the connected account's playlists and favorites.

Verified 24 actions OAuth available
Deezer website Platform Documentation Capability data verified 2026-08-28
The weekly refresh runs for the brand's public playlist
Search with the advanced syntax pulls candidates by artist, label, and duration bounds
Get Service Info reports the country Deezer resolved this connection to, which is what the whole catalog is scoped by
Get Track reads each candidate's playable flag, because a track that exists is not always a track that plays
Add Tracks To Playlist appends the additions that survived both checks
The curator gets the added list and the skipped list with a reason against each skip
The curator decides on removals, because taking a track out removes every copy of it in one call

What This Integration Enables

Deezer is a catalog first and a library second, and the connector reflects that split. Most of the surface is reading: search with a structured syntax that filters on artist, album, label, and duration or tempo bounds, plus albums, artists, tracks, charts, genres, editorial selections, radios, podcasts, and podcast episodes. A smaller set of operations writes, and only to the one account the connection is authorized for: creating, updating, and deleting playlists, adding and removing tracks, and managing favorites.

Two facts shape every workflow built on it. The catalog is scoped to the country Deezer resolves the caller to, with no parameter to override it, so a missing record is often a regional absence rather than an error. And the write permissions split in a way that is easy to miss: a connection that can create a playlist and add tracks to it does not automatically have the separate permission needed to delete a playlist or remove a favorite. FlowRunner agents can read the catalog all day. The writes are where a human-in-the-loop step earns its place.

Without FlowRunner

Curation is a browser tab Someone searches, listens, copies links, and pastes them into a playlist by hand every week
Region surprises A track that played fine for the person who added it is unavailable for half the audience, and nobody finds out
No record of why A playlist changes and the reasoning lives in the head of whoever changed it

With FlowRunner

Curation is a queued job The agent searches with structured criteria, checks availability, and proposes a list a person reviews
Region is checked, not assumed Availability is read per track against the country the connection actually resolves to
Every change has a reason Additions and skips are logged with the criterion that produced them before anything is written

Use Case Scenarios

A brand playlist that maintains itself

The brief lives in Airtable: a tempo range, a duration range, a label allowlist, and a rotation rule that says nothing stays more than eight weeks. Each week the agent runs Search with the advanced syntax to pull candidates, reads Get Track for each to confirm it is playable in the resolved country, and calls Get Playlist to see what is already there. Additions go in through Add Tracks To Playlist. The proposed removals go to the curator instead of executing, and the whole run is logged to Google Sheets so the playlist has a change history the platform does not keep.

Charts and editorial as a market signal

An agent pulls Get Chart and Get Editorial on a schedule for the genres the brand cares about, joins the result against the artists in the roster spreadsheet, and posts anything new into Slack with the position it entered at. Get Artist Related widens the same query to adjacent artists worth watching. Because charts are country scoped, the run states the resolved country in every digest rather than presenting a regional chart as a global one.

Opening a playlist to contributors

The team wants a playlist the wider community can add to for an event. The agent has everything it needs to make that change with Update Playlist, and it does not make it. Flipping a playlist to collaborative hands write access over that playlist to other Deezer users, and this connector has no operation that lists who added what or removes one contributor's edits.

Human-in-Loop Highlight

Update Playlist carries two flags that read like display preferences and are not. Public puts the playlist in front of everyone, including in search. Collaborative lets other Deezer users add and remove tracks inside it. The second one is the one worth stopping for, because it is a delegation of write authority to people the workflow has never seen, and nothing in the connector can enumerate them, attribute a change to one of them, or revoke a single contributor. The only remedies available are blunt: turn the flag back off, or delete the playlist, and deleting needs a separate permission this connection may not even hold. So the agent posts to the brand owner: "Making the Summer Sessions playlist collaborative will let any Deezer user add or remove tracks in it. There is no per contributor audit or revoke available through this connection, and removing a track later removes every copy of it. Turn it on, and for how long?" The owner decides. The agent does the rest of the maintenance unattended, because the rest of the maintenance is reversible.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

24 actions

Catalog

15
  • Search Searches the catalog with an advanced syntax that filters on artist, album, track, label, duration bounds, and tempo bounds, optionally restricted to one kind of record. Paging is by offset rather than page number.
  • Get Album Retrieves an album with its tracks and metadata.
  • Get Artist Retrieves an artist record.
  • Get Artist Related Retrieves one of the collections attached to an artist, such as top tracks, albums, or related artists, selected by a collection picker rather than spread across a dozen near identical operations.
  • Get Track Retrieves a track, including the flag that says whether it can actually be played in the resolved country. Existing and playable are not the same thing.
  • Get Playlist Retrieves a playlist with its tracks. The read behind every rotation and deduplication check.
  • Get Chart Returns the current chart for a genre or overall, scoped to the resolved country.
  • List Genres Lists the genres the catalog is organized by, which is what chart and editorial queries key on.
  • Get Editorial Returns Deezer's editorial selections, including new releases and curated picks.
  • List Radios Lists the radio stations available on the account's service.
  • Get Podcast Retrieves a podcast record from the catalog.
  • List Podcast Episodes Lists a podcast's episodes.
  • Get Episode Retrieves a single podcast episode.
  • Get Service Info Returns the country the caller was resolved to and whether the service is open there. The operation that explains a missing record, because a track absent in one region is legitimately present in another.
  • Get Streaming Options Returns the streaming capabilities available to the resolved service, which is what a workflow checks before assuming playback is possible.

Account

2
  • Get User Retrieves a user profile.
  • Get User Collection Retrieves one of the connected account's collections, such as playlists, favorite albums, favorite artists, or listening history, selected by a collection picker. Personal collections require the matching permission at connect time.

Library

7
  • Create Playlist Creates a playlist on the connected account.
  • Update Playlist Updates a playlist's title, description, and its public and collaborative flags. The collaborative flag delegates write access to other Deezer users, which is why this operation carries this page's human gate.
  • Delete Playlist Deletes a playlist. This needs a separate permission from the one that creates them, so a connection that can build playlists cannot necessarily remove them.
  • Add Tracks To Playlist Appends tracks to a playlist. The write behind every scheduled rotation.
  • Remove Tracks From Playlist Removes tracks from a playlist. It removes every copy of a track, so one that appears twice disappears entirely rather than losing a single instance.
  • Add To Favorites Adds an album, artist, track, playlist, radio, or podcast to the account's favorites. The connector maps the chosen type to the parameter name Deezer expects, because a generic identifier is accepted and then ignored.
  • Remove From Favorites Removes an item from favorites. Like deleting a playlist, this needs the separate removal permission.

Frequently Asked Questions

What can FlowRunner do with Deezer?

FlowRunner agents can run Search, Get Album, and Get Artist in Deezer, plus 21 more actions.

Does connecting Deezer to FlowRunner require OAuth?

Yes. Deezer connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Deezer trigger a FlowRunner workflow automatically?

Deezer doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Deezer

$100 in credits. No card required. Connect in minutes.