Skip to content
Spotify logoZoo logo

Connect Spotify to Zoo

Move data between Spotify and Zoo the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Spotify triggers
1
Spotify actions
15
Zoo triggers
0
Zoo actions
81

Automation ideas

What you can build with Spotify and Zoo

A few flows teams run between Spotify and Zoo. Use one as a starting point, or build your own from scratch.

  • Playlist Items Changed in Spotify creates Generate CAD Model in Zoo

    Triggers when the items of a playlist change

  • Playlist Items Changed in Spotify creates KCL Code Completions in Zoo

    Triggers when the items of a playlist change

  • Playlist Items Changed in Spotify creates Iterate CAD Model in Zoo

    Triggers when the items of a playlist change

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Spotify and acts in Zoo, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.