---
title: "Send Salesforce Deals for E-Signature with Flow | TurboDocx"
description: "Send Salesforce deals for e-signature automatically: add the free TurboSign Flow action to a record-triggered Flow on Opportunity and send on a stage change."
url: "https://www.turbodocx.com/guides/salesforce-flow-e-signature"
---

# How to send Salesforce deals for e-signature automatically with Flow

> To send Salesforce deals for e-signature automatically, install the free TurboSign for Salesforce app, build a record-triggered Flow on Opportunity, and add the **TurboSign: Send for Signature** action with two inputs: the record Id and the API name of a document setup. When a deal reaches the stage you pick, the Flow fills the contract from the opportunity and sends it to the signers in order. No rep clicks anything.

Salesforce Flow guide by Alex Martinez (Developer Relations & Automation Lead). Published November 9, 2026.

- Install (production or Developer Edition): https://github.com/TurboDocx/turbodocx-salesforce/releases/latest
- Source: https://github.com/TurboDocx/turbodocx-salesforce

## Can Salesforce send a contract for signature automatically?

Yes. Salesforce Flow can call an Apex action, and [TurboSign for Salesforce](https://www.turbodocx.com/integrations/salesforce-esignature.md) ships one for exactly this job. It is the same send a rep starts with the Send for Signature button, minus the button: the action generates the document from the record with the TurboDocx template in your document setup, sends it to the signers that setup names, and records a TurboSign Envelope on the opportunity.

That covers the question sales teams keep asking about workflow automation with e-signature steps: the signing step lives inside Salesforce automation you already own, so there is no export, no upload and no third tool to keep in sync. For the wider picture of automating the deal from quote to signature, see the [sales automation guide](https://www.turbodocx.com/resources/sales-automation-guide.md).

## How do you add the e-signature action to a record-triggered Flow?

Five steps. The first two are one-time setup an admin may already have done for manual sends; if so, start at step 3.

1. **Install the app and assign the permission sets.** Install TurboSign for Salesforce from the install link, add your TurboDocx API key and organization ID to the TurboDocx API External Credential, then assign TurboSign Admin to admins and TurboSign User to reps and to any integration or automation user whose changes will fire the Flow.
2. **Build and test a document setup.** On the TurboSign Setup tab, build a document setup for Opportunity: pick the template, map each value to an opportunity field, set the signers and the signing order, and test it on a real record. Note its Config API Name, for example Order_Form. The Flow passes that name to the action.
3. **Create a record-triggered Flow on Opportunity.** In Flow Builder, create a record-triggered Flow on the Opportunity object that runs when a record is updated. Set the entry condition to Stage equals the stage that should send the contract, such as Negotiation/Review or a custom Contract Sent stage, run it only when a record is updated to meet the condition, and optimize it for Actions and Related Records.
4. **Add the TurboSign: Send for Signature action.** Add an Action element and search for TurboSign: Send for Signature. Set Record Id to the triggering record, {!$Record.Id}, and Config Developer Name to the Config API Name of your document setup. Both inputs are required.
5. **Debug, activate and watch the first send.** Debug the Flow on a test opportunity in a sandbox, then activate it. Move a deal to the trigger stage and open the TurboSign Signatures panel on the record: the new envelope shows as sent, with the signers listed in order.

### The action at a glance

| Flow Builder label | Required | What to pass |
|---|---|---|
| Record Id | Yes | `{!$Record.Id}`, the opportunity that triggered the Flow |
| Config Developer Name | Yes | The Config API Name of the document setup, for example Order_Form |

The action returns no outputs. It queues the send in the background, because Salesforce does not allow a callout inside the save itself, and each queued job sends one record. Building the setup itself is covered in the setup docs: https://docs.turbodocx.com/docs/Integrations/turbosign-for-salesforce/setup

## Which deal workflows can you automate with an e-signature step?

- **Send the order form when Stage moves to Negotiation.** Entry condition: Stage equals Negotiation/Review, only when updated to meet it. The order form fills from the opportunity, account and owner, and the customer signer gets it the moment the rep moves the deal.
- **Send when a field changes, not just the stage.** Use any condition Flow supports, such as a Contract Ready checkbox turning true or an approval status changing to Approved, so legal or finance decides when the contract leaves.
- **Send from a data load or an integration.** When an integration user or a data import updates opportunities, the same Flow fires for each record. Give that user the TurboSign User permission set, and every qualifying deal gets its contract.

Every one of these depends on the contract filling itself correctly. If you have not mapped your fields yet, start with how to [fill contracts from opportunity data](https://www.turbodocx.com/resources/auto-populate-contracts-from-salesforce.md).

## Which user does the Flow run as, and what permissions does it need?

The callout to TurboDocx runs as whoever triggered the Flow: the rep who changed the stage, or the integration user behind a data load. That user needs the **TurboSign User** permission set, which grants access to the TurboDocx credential. Without it, the send fails with a credential error.

The app records that same user as Sent By on the envelope, and the signing request goes out with their name and email as the sender. A send fired by an integration user goes out under that user's name, so give it a name your customers will recognize.

Because nobody is watching a background send, failures are not shown on screen. A missing required value, a signer with no email or a setup name that does not exist is written to a TurboSign Log record. Check those after your first runs. The install guide (https://docs.turbodocx.com/docs/Integrations/turbosign-for-salesforce/install) covers the credential and permission sets in detail.

## What happens when the signer finishes?

Signers get the document in order, verify with an email code if your TurboDocx organization requires it, and sign in the browser or on their phone. The Salesforce app does not send SMS codes, and because it sends no phone numbers, a send fails if your organization's default code method is text message.

When everyone has signed, TurboDocx saves the signed PDF and the audit trail PDF to the opportunity's Files and runs the setup's optional On Completion update, for example Stage to Closed Won. That write-back of the signed copy and the stage update is on the Pro plan and up.

The TurboSign Envelope on the record tracks the request through sent, under review, completed, voided or expired. It refreshes when someone opens the TurboSign Signatures panel or clicks Refresh. To act on a voided or expired request, build a second Flow on the TurboSign Envelope Status field; the action list also includes TurboSign: Send Reminder, TurboSign: Void Envelope and TurboSign: Get Envelope Status.

## What does automated signing cost?

- The app is free and open source under the MIT license, on every plan.
- 5 signatures a month are free, including sends from a Flow.
- Saving the signed copy to the record and updating the stage is on the Pro plan and up.
- Flow sends use your API key, so they count toward the 60 API signatures a month listed for Pro.

API plans start at $0.30 per signature, with no minimums. Start on the free plan and pay only for the signatures you send beyond it, so a month with one extra signature costs $0.30.

The Flow action works on Enterprise, Unlimited, Performance and Developer editions, plus their sandboxes. Compare plans on the [pricing page](https://www.turbodocx.com/pricing.md) or read more about the [Salesforce e-signature app](https://www.turbodocx.com/integrations/salesforce-esignature.md).

## Salesforce Flow e-signature FAQ

### How can I push deals from my CRM to an e-signature platform automatically?

In Salesforce, install the free TurboSign for Salesforce app and build a record-triggered Flow on Opportunity that calls the TurboSign: Send for Signature action when the deal reaches a stage you choose. The action fills the contract from the opportunity and sends it to the signers in order, so nobody has to export the deal or upload a PDF.

### Does a rep have to review the document before the Flow sends it?

No. The Flow action sends without the review window a rep sees after clicking Send for Signature, so every required value must already be on the record. If a required value is empty or a signer has no email, that send fails and the error is written to a TurboSign Log record instead of going out incomplete.

### Can an integration user or a data load trigger the send?

Yes. The send runs as the user whose change fired the Flow, so assign the TurboSign User permission set to that integration or automation user. When many records qualify at once, the action queues them as one background job and sends one record at a time, which keeps a bulk update inside Salesforce limits. Developer Edition orgs cap that chain of jobs at a depth of five, so a large bulk update there sends only the first few records.

### Can a Flow send reminders or void a signature request?

Yes. The app includes TurboSign: Send Reminder, which emails the signers whose turn it is, and TurboSign: Void Envelope, which takes an Envelope Id and a Reason. TurboSign: Get Envelope Status returns the live status of an envelope.

### Which Salesforce editions can run the Flow action?

Enterprise, Unlimited, Performance and Developer Edition orgs, plus their sandboxes. Professional and Group editions are not supported, because custom Apex only runs there from a managed package that has passed the AppExchange security review.

## Related

- [TurboSign for Salesforce](https://www.turbodocx.com/integrations/salesforce-esignature.md): The free, open source Salesforce e-signature app behind this guide: send button, setups, security and plans.
- [Step-by-step guide to sending from Salesforce](https://www.turbodocx.com/guides/send-documents-for-signature-from-salesforce.md): The manual path: a rep clicks Send for Signature, reviews the values and previews the document.
- [Fill contracts from opportunity data](https://www.turbodocx.com/resources/auto-populate-contracts-from-salesforce.md): Map template values to opportunity, account and owner fields so every contract fills itself.
- [Sales automation guide](https://www.turbodocx.com/resources/sales-automation-guide.md): Where automated signing fits in the rest of the deal: proposals, quotes, contracts and handoff.

## Get started

Install the app, build one document setup, and drop the action into a Flow. The admin docs (https://docs.turbodocx.com/docs/Integrations/SalesForce#send-for-signature-with-turbosign-for-salesforce) walk through each screen. [Install free](https://github.com/TurboDocx/turbodocx-salesforce/releases/latest).

Talk to our team: https://www.turbodocx.com/demo