Automate eSignature workflows with Zapier
BoldSign’s Zapier integration automates eSignature workflows in both directions. A new lead in your CRM sends the agreement out for signing. When it comes back signed, your CRM, storage, and billing tools update without anyone touching them.
- Sends from your BoldSign templates
- Test every Zap in sandbox mode first
Trusted by 50,000+ businesses worldwide
What does an eSignature integration with Zapier do?
BoldSign’s Zapier integration connects your signing to thousands of apps, so signing steps run automatically. Its Zapier app has three instant triggers and one action that sends from a template.
Works in: Zapier, with Zaps you build in the Zapier editor.
Why choose BoldSign for Zapier users
BoldSign suits teams that run signing from another app. Every trigger is instant, and you pay for envelopes, not seats.
-
Every trigger is instant
Sent, completed, and declined reach Zapier the moment they happen, on any Zapier plan, with no polling delay.
-
You pay for envelopes, not seats
Billing follows the envelopes a Zap sends, so one subscription covers the whole team.
-
Automated sends stay auditable
The audit trail shows which documents a Zap sent. An automated contract stays as traceable as a manual one.
Triggers and actions in the Zapier app
BoldSign calls Zapier as soon as a document is sent, completed, or declined, on any Zapier plan. The table lists each trigger and the one action.
| Event | Type | What it does |
|---|---|---|
| Document Sent | Trigger, instant | Starts a Zap when you send a document for signature. |
| Document Completed | Trigger, instant | Starts a Zap once every signer has signed. |
| Document Declined | Trigger, instant | Starts a Zap when a signer declines the document. |
| Send Document From Template | Action | Sends a document for signature from a BoldSign template. |
Each trigger has an Admin mode setting. Turn it on to catch documents the whole organization sends.
How do you set up the Zapier integration?
BoldSign connects to Zapier inside a Zap, with no code to write. Build the template first, then follow 4 steps.
- 01
Build the template in BoldSign
Add your file, set each signer role, and place the fields the Zap will fill. Save the template.
- 02
Pick the app that starts the Zap
Create a Zap and choose the trigger app: a form, a sheet, a CRM, or BoldSign itself.
- 03
Add BoldSign and sign in
Choose BoldSign as the action app and Send Document From Template. Sign in to connect your BoldSign account.
- 04
Choose the template and map the fields
Pick your template, map each field and signer, then turn the Zap on.
How do you test a Zap before it sends real documents?
BoldSign gives every Zap a Sandbox Mode field. Set it to true and the Zap runs without using an envelope.
Sandbox mode sits in the Zap
Set Sandbox Mode to true while you build, then switch it to false when the Zap is ready.
The sandbox account is free
A free sandbox gives you full API access with no credit card.
Test documents clean themselves up
Sandbox documents carry a test watermark and are deleted after 14 days.
What teams automate with Zapier
BoldSign Zaps do one of two jobs. They send a contract when a record appears, or they file it once it is signed.
Send from a form entry
A form response sends the signature request, with the answers filled in.
See the Google Forms setupSend from a spreadsheet row
A new or updated sheet row sends the agreement to the person named in it.
See the Google Sheets setupFile the signed copy in storage
The signed PDF lands in Google Drive, Dropbox, or OneDrive.
Read the storage guideTell the team in Slack
A Slack message goes out when a document is sent.
See seven workflow ideasKeep the CRM record current
A CRM deal moves on once the contract comes back signed.
Read the CRM guideTrack every request in a sheet
Each request writes a row with the recipient, date, and status.
See the tracking setup
Limits and costs to know before you automate with BoldSign
Live Zaps need the BoldSign Enterprise API plan. Prices are in USD.
- $30 a month, Enterprise API plan Includes 40 envelopes a month. Each envelope after that is $0.75.
Before your first Zap
- 1 action in the Zapier app Send Document From Template. A Zap cannot send a file that has no template.
- 3 triggers in the Zapier app Sent, completed, and declined. No trigger fires for a reminder or an expiry.
- The 30-day trial runs in sandbox mode only and cannot send live documents through a Zap.
- The Document Completed trigger cannot download a teammate’s signed PDF without the View Document permission.
- Production accounts can make 2,000 BoldSign API requests an hour.
How are documents kept secure when a Zap sends them?
A document a Zap sends carries the same BoldSign controls as one you send by hand. The audit trail records it, and your account’s compliance settings still apply.
Compliance
BoldSign meets global security and compliance standards to protect your documents and data. Manage the settings below to align with your organization’s requirements.
Data Residency
Active (US - Global)Your documents and signer data are securely stored in your selected region to meet data sovereignty and local regulatory requirements.
HIPAA Compliance
EnabledEnable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.
PCI DSS
CompliantPayments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.
CCPA & CPRA
CompliantEnsures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.
SOC 2 Type II
CompliantBoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.
UETA & ESIGN
CompliantBoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).
eIDAS (SES)
CompliantBoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.
eIDAS (QES)
EnabledEnable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.
Security and procurement documents for eSignature
IT and procurement teams can read BoldSign’s security policy, data processing agreement, and subprocessor list online. They can also request the SOC 2 Type 2 report.
- Sign-in
Single sign-on and user provisioning
Works with Microsoft Entra ID.
See features by plan - Audit report
SOC 2 Type 2 report
Available on request from BoldSign.
Request the SOC 2 report - Data protection
Data processing agreement
Includes the EU Standard Contractual Clauses and the UK Addendum by reference.
Read the data processing agreement - Data protection
Subprocessor list
Every third party BoldSign uses to process data.
See the subprocessor list - Service
Service level agreement
Uptime, support response times, and service commitments.
Find it in the Legal Center
More guides for automating eSignatures with Zapier
BoldSign publishes guides for the Zaps teams build most often. The rest of the cards cover its other automation routes.
- Guide
Seven workflow automation ideas
Zaps for sales, HR, and operations teams.
Read the ideas - Help centre
Every Zapier setup article
Setup steps for forms, sheets, storage, and CRMs.
Open the help centre - Integration
Power Automate
The same jobs in Microsoft Power Automate.
See Power Automate - Developers
BoldSign eSignature API
Build the workflow in your own code.
See the API - AI
BoldSign in Claude and other assistants
Send from a template through the BoldSign MCP server.
See BoldSign MCP - Comparisons
Moving from another eSignature tool
How BoldSign compares with the tools teams switch from, side by side.
See all comparisons - Hub
All eSignature integrations
CRM, storage, accounting, automation, and messaging apps.
See all integrations
Questions teams ask about eSignature in Zapier
Does BoldSign work with Zapier?
Yes. BoldSign is listed in the Zapier app directory with three triggers and one action. That connects it to the other apps in your integration stack.
Can a Zap send a file that is not a template?
No. The action sends from a BoldSign template only. Build a template for each document you send often, and map its fields in the Zap.
Can I track documents the whole team sends?
Yes. Turn Admin mode on in the trigger. For a teammate’s signed PDF, the owner grants View Document for all teams. See the admin mode guide.
Do signers need a Zapier or BoldSign account?
No. Signers open the link in the signature request email and sign on any device. See how signing works for recipients.
Can an AI assistant send a document through Zapier?
Yes. Zapier MCP exposes the Send Document From Template action to an MCP client. BoldSign also runs its own MCP server for assistants.
What happens if a Zap fails with a permission error?
A permission error means the plan cannot send live. Check the plan, then check Sandbox Mode. The error guide lists both causes.
Build your first signing Zap today
Start in the free BoldSign sandbox, test the Zap end to end, then switch it live.
- 30-day free trial
- No credit card required
Last updated: October 17, 2026.