Zapier integration
Connect EndorsedSign to Zapier workflows with a tenant-scoped API key: trigger on signing events and run send actions without building a custom middleware service.
Current marketplace coverage
Public integrations are rolled out in sequence. This table reflects what ships in product today vs what is still in delivery.
| Ecosystem | Status | What is available now |
|---|---|---|
| Zapier | ✅ Live connector | Tenant API-key auth, four triggers (template created, document signed/completed/expired), and two actions (create from template, send for signing). |
| Make.com | 🗓️ In delivery | Planned module set is still in delivery. Not publicly available yet. |
| n8n | 🗓️ Planned | No public module today. Prioritization depends on activated-tenant demand from marketplace sources. |
Setup in three steps
- 1
Claim or choose a tenant API key
Use Admin → Developer → API Keys (or the sandbox quickstart) and mint a key with the `integrations:zapier` scope. Tenant identity is derived from that key, never from Zap input fields.
- 2
Connect in Zapier
Paste the API key into the EndorsedSign app connection. Validate with the auth test call and pick the trigger/action pair that matches your workflow.
- 3
Verify operational behavior
Run a full test: create/send from Zapier, complete a signing session, and confirm lifecycle events in your downstream system plus Developer Console traces.
What teams build with it
Template-to-signing automation
When a deal reaches a stage in your CRM, create a document from a template and send it instantly for signing.
Post-signature handoff
On `document.completed`, fan out to finance, onboarding, or archive systems with your existing Zapier automations.
Operations notifications
Route signed, expired, or declined events into Slack and ticketing systems so teams act before deals stall.
Integration marketplace FAQ
Get the key, then connect in minutes
Claim a sandbox, mint an `integrations:zapier` key, and run a full send-and-sign loop before wiring production systems.