Built by people who live in the Maestro API.

Baton is built by Fluidlabs, a Docusign IAM implementation and integration partner. Fluidlabs ships Docusign Maestro Extension Apps used by enterprise customers across CRM, construction, finance, and HR. We've been a Docusign App Center publisher since 2024.

We know the Maestro API intimately because we've spent years inside it. Every Extension App we built started from the same problem: a customer needed something to fire a Maestro workflow on a specific event in their CRM, ATS, procurement system, or ticketing tool. Maestro itself is excellent at orchestration. But the trigger - the part that says "something just happened over here, fire this workflow over there" - had no native bridge.

We solved that bridge for one client. Then a second. Then twenty. By the time we were rebuilding the same webhook reception, signature verification, and Maestro launch logic for the fourth time, we knew this should be a product.

Maestro should run the show. Baton triggers Maestro workflows, then gets out of the way. Document orchestration, routing, signing, and write-back all happen in Docusign where they belong. We don't replace Maestro - we make it easier to start.

Webhook URLs over OAuth into source platforms. Baton authenticates only to Docusign. Source platforms send webhooks; we never store credentials for HubSpot, Salesforce, or anywhere else. Less to secure, less to break, less to audit.

Operations teams need observability, not just automation. When 200 contracts a month run through your stack automatically, the question stops being "can we automate this?" and becomes "which one stalled last Thursday and why?" Baton's Command Center is built for the second question.