Can Parseur and Zoo talk in both directions?

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

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

Parseur triggers: 5
Parseur actions: 6
Zoo triggers: 0
Zoo actions: 81

Automation ideas

What you can build with Parseur and Zoo

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

New Document Processed in Parseur creates Generate CAD Model in Zoo
Fires when a new document is successfully processed and parsed by Parseur.
New Document Processed in Parseur creates KCL Code Completions in Zoo
Fires when a new document is successfully processed and parsed by Parseur.
New Document Processed in Parseur creates Iterate CAD Model in Zoo
Fires when a new document is successfully processed and parsed by Parseur.
New Table Field Processed in Parseur creates Generate CAD Model in Zoo
Fires when a document with table fields is processed, and triggers for each row (table field) separately.