Skip to content
Checkout.com logoZoo logo

Connect Checkout.com to Zoo

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

Checkout.com triggers
2
Checkout.com actions
7
Zoo triggers
0
Zoo actions
81

Automation ideas

What you can build with Checkout.com and Zoo

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

  • Payment Events in Checkout.com creates Generate CAD Model in Zoo

    Trigger order fulfillment when payment is approved.

  • Payment Events in Checkout.com creates KCL Code Completions in Zoo

    Trigger order fulfillment when payment is approved.

  • Payment Events in Checkout.com creates Iterate CAD Model in Zoo

    Trigger order fulfillment when payment is approved.

  • Dispute Events in Checkout.com creates Generate CAD Model in Zoo

    Notify operations upon dispute opening or resolution.

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 Checkout.com 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.