Music for everyone
Spotify currently provides 1 trigger that can start a workflow and 15 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Playlist Items Changed
Triggers when the items of a playlist change
Search
Searches for tracks, artists, albums, etc.
Get Playback State
Retrieves the current playback state of the player
Play / Resume
Resumes or starts playback
Pause
Pauses the playback
Set Volume
Sets the volume of the player
Get Playlists
Retrieves the list of playlists that you created or followed
Get Playlist Info
Retrieves details of a playlist
Get Playlist Items
Retrieves the list of items in the playlist
Get Saved Tracks
Retrieves the list of saved tracks for the current user
Create Playlist
Creates a new playlist for the current user
Update Playlist
Updates details of the playlist
Add items to playlist
Adds tracks or episodes to the playlist
Remove items from playlist
Removes tracks or episodes from the playlist
Reorder playlist
Reorders items in the playlist
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Spotify event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Playlist Items Changed
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Spotify action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Search
Combine Spotify with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
Playlist Items Changed
Finishes with
Search, then preserve the outcome in Coherence
The exact authentication fields depend on Spotify. The workflow structure stays straightforward:
Authorize the Spotify account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Spotify or provide a complementary trigger or action.
Spotify currently provides 1 trigger that can start a workflow and 15 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Spotify currently lists 1 trigger and 15 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Spotify triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
