Skip to content
SendPulse logoZoo logo

Connect SendPulse to Zoo

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

SendPulse triggers
3
SendPulse actions
6
Zoo triggers
0
Zoo actions
81

Automation ideas

What you can build with SendPulse and Zoo

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

  • New Subscriber in SendPulse creates Generate CAD Model in Zoo

    Fires when new subscriber is added

  • New Subscriber in SendPulse creates KCL Code Completions in Zoo

    Fires when new subscriber is added

  • New Subscriber in SendPulse creates Iterate CAD Model in Zoo

    Fires when new subscriber is added

  • New Unsubscriber in SendPulse creates Generate CAD Model in Zoo

    Fires when subscriber unsubscribes

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 SendPulse 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.