---
title: "E-Signing made simple with BoldSign and Power Automate"
description: "Integrate Power Automate with BoldSign to simplify eSignatures, automate contract workflows, reduce manual work & accelerate secure document approvals easily."
url: "https://boldsign.com/integrations/power-automate/"
---

Power Automate integration

# 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.

[Start in the free sandbox](https://account.boldsign.com/signup?planId=1076)[Book a walkthrough](https://boldsign.com/request-demo.md)

- Published in the Microsoft Power Platform connector list
- Test every flow in sandbox mode first

A two-step flow. The first step watches SharePoint for a new item. The second step is the BoldSign action, set to send a vendor onboarding agreement from a template to Michael Brooks.

Trusted by 100,000+ organizations worldwide

![Samsonite](https://boldsign.com/assets/landing/trustbar/samsonite.svg)

![Ryanair](https://boldsign.com/assets/landing/trustbar/ryanair.svg)

![Hyatt](https://boldsign.com/assets/landing/trustbar/hyatt.svg)

![Sony](https://boldsign.com/assets/landing/trustbar/sony.svg)

![Crumbl Cookies](https://boldsign.com/assets/landing/trustbar/crumbl.svg)

![Payroc](https://boldsign.com/assets/landing/trustbar/payroc.svg)

![Cost Plus](https://boldsign.com/assets/landing/trustbar/costplus.svg)

What it is

## 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.

Operations

## 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.

Setup

## 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. 01

   ### Prepare the template

   Upload your file and name each signer role. Drop in the fields the flow will fill, then save the [template](https://boldsign.com/electronic-signature-features/templates.md).

2. 02

   ### Create the BoldSign connection

   In Power Automate, open Connections and search for BoldSign. Choose the region your account sits in, then sign in.

3. 03

   ### 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. 04

   ### 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. 05

   ### Test the flow, then save it

   Run the flow once with sandbox mode on. Check the result, switch sandbox mode off, and save.

Testing

## 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.

In practice

## 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 setup](https://support.boldsign.com/kb/article/20327/how-to-automatically-save-completed-documents-to-team-specific-sharepoint-folders-using-power-automate)

- ### Keep the signer attachments

  Files a signer uploads are pulled out of the completed document and stored with it.

  [See the attachments setup](https://support.boldsign.com/kb/article/19717/how-to-download-attachments-from-a-completed-document-using-rest-apis-in-power-automate)

- ### Update the board that tracks the deal

  A work item moves on once the document is signed.

  [See the board setup](https://support.boldsign.com/kb/article/18847/integrate-boldsign-with-mondaycom-using-power-automate)

- ### Send from a new record

  A new list item or form entry raises the request for whoever it names.

  [Read the setup guide](https://boldsign.com/blogs/how-to-integrate-boldsign-with-power-automate.md)

Why BoldSign

## 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.

What it costs

## 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.

[See Enterprise API pricing](https://boldsign.com/electronic-signature-pricing/?plan=api)

Good to know

## Before your first flow

- 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.

* 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.

Security

## 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.

Settings

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.

- ![US flag](https://boldsign.com/assets/landing/compliance/residency-de93bd.svg) 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.

  [View Data Residency Policy](https://boldsign.com/security-policy.md)

- ![HIPAA logo](https://boldsign.com/assets/landing/compliance/hipaa-c34e9b.png) HIPAA Compliance

  Enabled

  Enable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.

  [View Details](https://boldsign.com/hipaa-overview.md)

- ![PCI DSS logo](https://boldsign.com/assets/landing/compliance/pci-960f14.png) PCI DSS

  Compliant

  Payments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.

  [View PCI DSS Policy](https://boldsign.com/security-policy.md)

- ![CCPA logo](https://boldsign.com/assets/landing/compliance/ccpa-e62333.png) CCPA & CPRA

  Compliant

  Ensures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.

  [View Privacy Policy](https://boldsign.com/privacy-policy.md)

- ![AICPA SOC logo](https://boldsign.com/assets/landing/compliance/soc2-b31494.png) SOC 2 Type II

  Compliant

  BoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.

  [Request SOC 2](https://boldsign.com/soc2-overview.md)

- ![US flag](https://boldsign.com/assets/landing/compliance/esign-de93bd.svg) UETA & ESIGN

  Compliant

  BoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).

  [View UETA & ESIGN Policy](https://boldsign.com/ueta-and-esign-act-compliance.md)

- ![EU flag](https://boldsign.com/assets/landing/compliance/eidas-ses-677fe1.svg) eIDAS (SES)

  Compliant

  BoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.

  [View SES Policy](https://boldsign.com/simple-electronic-signature-compliance.md)

- ![EU flag](https://boldsign.com/assets/landing/compliance/eidas-qes-677fe1.svg) eIDAS (QES)

  Enabled

  Enable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.

  [View QES Policy](https://boldsign.com/qes-overview.md)

The compliance panel in your BoldSign account.

For IT and procurement

## Security and procurement documents for eSignature

IT and procurement teams can read BoldSign’s [security policy](https://boldsign.com/security-policy.md), 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](https://boldsign.com/electronic-signature-pricing/?plan=webapp)

- Audit report

  ### SOC 2 Type 2 report

  Available on request from BoldSign.

  [Request the SOC 2 report](https://boldsign.com/compliance-request-form.md)

- Data protection

  ### Data processing agreement

  Includes the EU Standard Contractual Clauses and the UK Addendum by reference.

  [Read the data processing agreement](https://boldsign.com/dpa.md)

- Data protection

  ### Subprocessor list

  Every third party BoldSign uses to process data.

  [See the subprocessor list](https://boldsign.com/subprocessors.md)

- Service

  ### Service level agreement

  Uptime, support response times, and service commitments.

  [Find it in the Legal Center](https://boldsign.com/legalcenter.md)

Related

## 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](https://boldsign.com/blogs/how-to-integrate-boldsign-with-power-automate.md)

- Help centre

  ### Supported triggers and actions

  Every event and action, with what each one returns.

  [Open the help centre](https://support.boldsign.com/kb/article/18796/what-are-the-supported-boldsign-triggers-and-actions-in-power-automate)

- Webinar

  ### Document approval workflows

  A recorded session on approval flows for document teams.

  [Watch the webinar](https://boldsign.com/webinars/power-automate-document-approval-workflow.md)

- Integration

  ### Zapier

  The same jobs outside the Microsoft stack.

  [See Zapier](https://boldsign.com/integrations/zapier.md)

- Developers

  ### BoldSign eSignature API

  Write the same workflow directly against the API.

  [Read the API docs](https://boldsign.com/esignature-api.md)

- AI

  ### BoldSign in Claude and other assistants

  Let an AI assistant raise the request through the MCP server.

  [See BoldSign MCP](https://boldsign.com/mcp-ai-esignature-assistant.md)

- Hub

  ### All eSignature integrations

  Every app BoldSign connects to, grouped by what it does.

  [See all integrations](https://boldsign.com/integrations.md)

Common questions

## 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](https://boldsign.com/integrations.md).

### Can a flow send a document that is not a template?

No. Sending runs from a BoldSign [template](https://boldsign.com/electronic-signature-features/templates.md), 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](https://support.boldsign.com/kb/article/20327/how-to-automatically-save-completed-documents-to-team-specific-sharepoint-folders-using-power-automate) 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](https://support.boldsign.com/kb/article/18796/what-are-the-supported-boldsign-triggers-and-actions-in-power-automate) 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](https://support.boldsign.com/kb/article/575).

### 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](https://boldsign.com/electronic-signature-features/branding.md) can be applied in the same step.

Get started

## 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.

[Start in the free sandbox](https://account.boldsign.com/signup?planId=1076)[Book a walkthrough](https://boldsign.com/request-demo.md)

- 30-day free trial
- No credit card required

*Picture: A completed employment contract: signed by John Doe on 11/03/2026, all parties have signed*

Last updated: October 17, 2026.
