eSignBase Is Now on Zapier: Automate Document Signing Without Writing Code
When we started building eSignBase, the target user was clear: a developer integrating document signing into an automated platform via REST API.
But not every team that needs automated e-signatures has a developer available — or wants to write code for every workflow.
That’s why I’m excited to announce that eSignBase is now officially available on Zapier.
What This Means
Zapier connects apps. If you’ve ever set up a “when X happens in app A, do Y in app B” automation, you already know how it works.
With the eSignBase Zapier integration, you can now trigger document signing workflows from thousands of tools — without writing a single line of code. If you’re a developer who prefers working directly with the API, the REST API is still there for you.
Some examples of what’s now possible:
- A new row appears in Google Sheets → a contract is sent for signature automatically
- A deal reaches “Closed Won” in your CRM → an agreement is dispatched instantly
- A contact submits a Typeform → a compliance document is sent to them for signing
- A new hire is added in an HR tool → an employment contract is triggered
If your signing workflow currently involves a human manually sending documents, there’s a good chance Zapier can automate it.
What the Integration Includes
Trigger: Document Completed
When a recipient finishes signing a document in eSignBase, Zapier detects it automatically.
This lets you build downstream automations — like notifying a Slack channel, updating a CRM record, moving a row in a spreadsheet, or kicking off an onboarding sequence — the moment a document is signed.
Action: Send Document
This is the core of most workflows. You can send a signing request directly from a Zap:
- Pick a template from your eSignBase account (loaded dynamically)
- Select the role the recipient should fill (also dynamic, based on the template)
- Map in the recipient’s name and email from whatever app triggered the Zap
The document is created and sent — the same as if you had called the REST API directly, but configured entirely through the Zapier UI.
How Authentication Works
The integration uses OAuth2 Authorization Code flow. When you connect eSignBase to Zapier, you’ll be redirected to your eSignBase account to log in and authorize access.
Your credentials stay yours. Zapier receives a token scoped to your account — no credentials are shared, and tokens refresh automatically in the background.
Credits Still Work the Same Way
One thing that doesn’t change: the pay-as-you-go model.
Each document signing workflow triggered through Zapier consumes exactly one credit — the same as using the REST API or the web UI directly.
No subscription required. No per-seat fee for the integration. You pay only when a document is actually sent.
Getting Started
- Go to Zapier
- Connect your account using OAuth2 (you’ll be redirected to eSignBase to log in)
- Create a Zap using the Send Document action or Document Completed trigger
- Map your template, recipient fields, and you’re done
If you don’t have an eSignBase account yet, you can sign up and test the integration in sandbox mode first — no credits consumed during testing.
Pre-built Zap templates for common workflows are on the way — making it even faster to get started.
Why This Matters
The REST API will always be the best choice for teams building document signing directly into their product.
But not every workflow lives inside a product codebase. Sometimes a document needs to go out because of a form submission, a spreadsheet update, or a CRM stage change — and that’s exactly where Zapier fits.
For EU-based teams or Companies that work with EU based customers, there’s an additional consideration: eSignBase runs on EU infrastructure, and every document signed through it — whether via Zapier, the REST API, or the web UI — is eIDAS-compliant and subject to EU data governance. That’s something the larger US-based e-signature platforms can’t offer, regardless of how you trigger the workflow.
With this integration, eSignBase is now accessible to operations teams, legal teams, HR teams, and anyone else who needs reliable, eIDAS-compliant e-signatures as part of their existing toolstack — no engineering involvement required.