Automate eSignature workflows with Power Automate
Turn a new record, approval, or form response into a signed agreement automatically. The completed document lands straight in SharePoint, OneDrive, or Teams, with no one chasing a signature by hand.
- Published in the Microsoft Power Platform connector list
- Test every flow in sandbox mode first
Trusted by 50,000+ businesses worldwide
What does an eSignature integration with Power Automate do?
BoldSign’s Power Automate integration links your signing into Microsoft flows, so signing runs automatically. BoldSign publishes a connector with one trigger and four actions for sending, checking status, and downloading files.
Works in: Microsoft Power Automate, through the BoldSign connector.
Triggers and actions in the Power Automate connector
One BoldSign trigger covers every document event. You pick the events when you add it, and BoldSign calls your flow as they happen.
| Operation | Type | What it does |
|---|---|---|
| Webhook Events | Trigger | Starts a flow when one of the document events you picked happens. |
| Send document using template with recipient | Action | Sends a signature request built from a BoldSign template. |
| Get document status | Action | Returns the current status and details of a document. |
| Download Document | Action | Downloads the PDF file of a document. |
| Download AuditTrail | Action | Downloads the audit trail of a completed document. |
Events you can pick in the trigger
- Document sent
- Document signed
- Document completed
- Document declined
- Document revoked
- Document reassigned
- Document expired
- Authentication failed
- Delivery failed
- Send failed
- Template send failed
- Draft created
Turn on team events in the trigger to catch documents your teammates send. Account admins then see events across the organization.
How do you set up the Power Automate integration?
BoldSign connects inside the flow, and nothing has to be coded. Create the template first, then work through 5 steps.
- 1
Prepare the template
Upload your file and name each signer role. Drop in the fields the flow will fill, then save the template.
- 2
Create the BoldSign connection
In Power Automate, open Connections and search for BoldSign. Choose the region your account sits in, then sign in.
- 3
Choose what starts the flow
Pick a BoldSign document event as the trigger. The flow can also start from a list, a form, or a message in another app.
- 4
Add the BoldSign action
Add the action your flow needs and pick the template. Map each signer and field to the values the trigger passes in.
- 5
Test the flow, then save it
Run the flow once with sandbox mode on. Check the result, switch sandbox mode off, and save.
How do you test a flow before it sends real documents?
BoldSign’s send action carries a Sandbox Mode field. Switch it on and the whole flow runs, but no live document leaves BoldSign.
The switch sits in the action
Leave sandbox mode on while you build, and turn it off the day you go live.
A sandbox account costs nothing
The BoldSign sandbox plan opens full API access and asks for no card.
Test files do not pile up
Each sandbox document is watermarked as a test, and BoldSign deletes it after 14 days.
What teams build with Power Automate
Teams build two kinds of BoldSign flow. Some raise a signature request from a new record. Others take over once the signed copy arrives.
File signed copies by team
Each completed document lands in the SharePoint folder that owns it.
See the SharePoint setupKeep the signer attachments
Files a signer uploads are pulled out of the completed document and stored with it.
See the attachments setupUpdate the board that tracks the deal
A work item moves on once the document is signed.
See the board setupSend from a new record
A new list item or form entry raises the request for whoever it names.
Read the setup guide
Why choose BoldSign for Power Automate users
BoldSign fits teams whose signing already starts inside a flow. Every document event is covered, and billing follows envelopes, not seats.
-
One trigger, twelve events
Sent, signed, completed, declined, revoked, expired, and six more events can each start a flow.
-
The flow sends as the right person
The send action can send on behalf of a teammate, under the brand you choose for that document.
-
Billing follows envelopes, not seats
Billing follows the envelopes a flow sends, so one subscription covers the whole company.
Limits and costs to check before your first flow
A live flow needs the Enterprise API plan on the BoldSign side. Prices are in USD.
- $30 a month for the Enterprise API plan Covers 40 envelopes a month. Every envelope beyond that costs $0.75.
- 100 calls per connection, every 60 seconds Power Automate throttles a flow that passes this rate.
- 4 actions in the connector No action sends a reminder, revokes a document, or builds a template.
Before your first flow
- BoldSign is a premium connector, so your Power Automate plan has to include premium connectors.
- A BoldSign connection cannot be shared. Everyone who uses a shared app makes their own connection.
- Production accounts can make 2,000 BoldSign API requests an hour.
How are documents a flow sends kept secure?
A flow sends through your own BoldSign account, so every control you already set still applies. BoldSign encrypts each document twice with AES-256. Its security controls are independently audited for SOC 2 Type 2. Each standard is listed in your account's Compliance page, shown below.
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 eSignature flows in Power Automate
BoldSign documents the flows teams ask about most. The last cards point to its other routes into automation.
- Guide
Set up the integration step by step
The full walkthrough, with an onboarding example.
Read the walkthrough - Help centre
Supported triggers and actions
Every event and action, with what each one returns.
Open the help centre - Webinar
Document approval workflows
A recorded session on approval flows for document teams.
Watch the webinar - Integration
Zapier
The same jobs outside the Microsoft stack.
See Zapier - Developers
BoldSign eSignature API
Write the same workflow directly against the API.
Read the API docs - AI
BoldSign in Claude and other assistants
Let an AI assistant raise the request through the MCP server.
See BoldSign MCP - Hub
All eSignature integrations
Every app BoldSign connects to, grouped by what it does.
See all integrations
Questions teams ask about eSignature in Power Automate
Does BoldSign work with Power Automate?
Yes. BoldSign publishes a connector for Power Automate, listed in the Power Platform directory. It has one document event trigger and four actions. That puts signing in reach of the apps you have already connected.
Can a flow send a document that is not a template?
No. Sending runs from a BoldSign template, so each automated request uses wording your team already approved. Save a template for every agreement the flow will raise.
Which apps can I connect through this integration?
Any app you already have in Power Automate, such as SharePoint, OneDrive, Outlook, or Teams. The SharePoint guide shows one end to end.
Can I catch documents my teammates send?
Yes. Turn on team events in the trigger, and your flow also sees what your teammates send. The triggers article lists every event.
Do signers need a Microsoft or BoldSign account?
No. Each signer opens the link in their email and signs from any device, with nothing to install. See what a recipient sees.
Can one flow send on behalf of another user?
Yes. The send action has an On behalf of field, so the request goes out under that colleague’s name. Their brand can be applied in the same step.
Build your first signing flow today
Start in the free BoldSign sandbox and test the flow end to end. Switch sandbox mode off when it works.
Last updated: October 17, 2026.