Skip to content
Respond.io logoZoo logo

Connect Respond.io to Zoo

Move data between Respond.io 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.

Respond.io triggers
7
Respond.io actions
9
Zoo triggers
0
Zoo actions
81

Automation ideas

What you can build with Respond.io and Zoo

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

  • Contact Tag Updated in Respond.io creates Generate CAD Model in Zoo

    Triggers when a tag is added or removed from a contact in Respond.io.

  • Contact Tag Updated in Respond.io creates KCL Code Completions in Zoo

    Triggers when a tag is added or removed from a contact in Respond.io.

  • Contact Tag Updated in Respond.io creates Iterate CAD Model in Zoo

    Triggers when a tag is added or removed from a contact in Respond.io.

  • Contact Updated in Respond.io creates Generate CAD Model in Zoo

    Triggers when an existing contact is updated in Respond.io.

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 Respond.io 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.