Can Pubrio and Zoo talk in both directions?

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

Move data between Pubrio 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 Pubrio Explore Zoo

Pubrio triggers: 1
Pubrio actions: 28
Zoo triggers: 0
Zoo actions: 81

Automation ideas

What you can build with Pubrio and Zoo

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

Monitor Event (Webhook) in Pubrio creates Generate CAD Model in Zoo
Triggers once per signal (signal_first mode) or once per company (company_first mode) when a Pubrio monitor fires. Copy the webhook URL into your Pubrio monitor destination configuration.
Monitor Event (Webhook) in Pubrio creates KCL Code Completions in Zoo
Triggers once per signal (signal_first mode) or once per company (company_first mode) when a Pubrio monitor fires. Copy the webhook URL into your Pubrio monitor destination configuration.
Monitor Event (Webhook) in Pubrio creates Iterate CAD Model in Zoo
Triggers once per signal (signal_first mode) or once per company (company_first mode) when a Pubrio monitor fires. Copy the webhook URL into your Pubrio monitor destination configuration.