Can OpenPhone and Zoo talk in both directions?

Yes. Build one flow that starts in OpenPhone 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.

Connect OpenPhone to Zoo

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

Start building Explore OpenPhone Explore Zoo

OpenPhone triggers: 5
OpenPhone actions: 4
Zoo triggers: 0
Zoo actions: 81

Automation ideas

What you can build with OpenPhone and Zoo

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

Call Recording Completed in OpenPhone creates Generate CAD Model in Zoo
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
Call Recording Completed in OpenPhone creates KCL Code Completions in Zoo
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
Call Recording Completed in OpenPhone creates Iterate CAD Model in Zoo
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
Outgoing Message Delivered in OpenPhone creates Generate CAD Model in Zoo
Fires when an outbound message is delivered successfully. Useful for message confirmation workflows.