Can Docusign and Zoo talk in both directions?

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

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

Docusign triggers: 11
Docusign actions: 8
Zoo triggers: 0
Zoo actions: 81

Automation ideas

What you can build with Docusign and Zoo

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

Signing Request Created in Docusign creates Generate CAD Model in Zoo
Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.
Signing Request Created in Docusign creates KCL Code Completions in Zoo
Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.
Signing Request Created in Docusign creates Iterate CAD Model in Zoo
Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.
Signing Request Sent in Docusign creates Generate CAD Model in Zoo
Triggers when a signing request is emailed out to recipients for the first time.