Connect setlist.fm and Spotify with fixes and improvements from sonallux
Describe what you want to happen between setlist.fm and Spotify with fixes and improvements from sonallux in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
setlist.fm
15 documented operations. See all setlist.fm operations
- GETGet a complete list of all supported countries
/1.0/search/countries - GETSearch for a city
/1.0/search/cities - GETSearch for venues
/1.0/search/venues - GETSearch for artists
/1.0/search/artists - GETSearch for setlists
/1.0/search/setlists - GETGet a user by userId
/1.0/user/{userId}
Spotify with fixes and improvements from sonallux
89 documented operations. See all Spotify with fixes and improvements from sonallux operations
- POSTAdd Item to Playback Queue
/me/player/queue - POSTCreate Playlist
/users/{user_id}/playlists - POSTAdd Items to Playlist
/playlists/{playlist_id}/tracks - DELETERemove User's Saved Shows
/me/shows - PUTSave Shows for Current User
/me/shows - DELETERemove Users' Saved Albums
/me/albums
How a setlist.fm and Spotify with fixes and improvements from sonallux automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in setlist.fm and Spotify with fixes and improvements from sonallux, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- OData for namespace microsoft.graph and setlist.fm11,427 operations
- OData for namespace microsoft.graph and Spotify with fixes and improvements from sonallux11,501 operations
- Cloudflare and setlist.fm3,137 operations
- Cloudflare and Spotify with fixes and improvements from sonallux3,211 operations
- NetBox and setlist.fm859 operations
- NetBox and Spotify with fixes and improvements from sonallux933 operations
- GitHub and setlist.fm826 operations
- GitHub and Spotify with fixes and improvements from sonallux900 operations
- Mist and setlist.fm783 operations
- Mist and Spotify with fixes and improvements from sonallux857 operations
Questions about connecting setlist.fm and Spotify with fixes and improvements from sonallux
- Can setlist.fm connect with Spotify with fixes and improvements from sonallux?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect setlist.fm to Spotify with fixes and improvements from sonallux?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate setlist.fm and Spotify with fixes and improvements from sonallux?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across setlist.fm and Spotify with fixes and improvements from sonallux?
- setlist.fm publishes 15 documented operations and Spotify with fixes and improvements from sonallux publishes 89. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either setlist.fm or Spotify with fixes and improvements from sonallux is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for setlist.fm and Spotify with fixes and improvements from sonallux. Descriptions are each provider’s own words, not ours.