---
title: "Send Documents for Signature from Salesforce | TurboDocx"
description: "Send documents for signature from Salesforce in 9 steps: install the free app, add your API key, build a document setup, then send from an opportunity."
url: "https://www.turbodocx.com/guides/send-documents-for-signature-from-salesforce"
---

# How to send documents for signature from Salesforce

> To send documents for signature from Salesforce, install the free TurboSign for Salesforce app, store your TurboDocx API key in Salesforce, and build a document setup on the TurboSign Setup tab. From then on a rep opens an opportunity, clicks Send for Signature, checks the values filled from the record, previews the contract and clicks Send. Signers sign in order from an email link. On the Pro plan and up, the signed PDF and audit trail land back on the opportunity and, if your admin sets it up, the stage moves to Closed Won.

Guide by Alex Martinez (Developer Relations & Automation Lead at TurboDocx). Published November 9, 2026.

Overview of the app: [TurboSign for Salesforce](https://www.turbodocx.com/integrations/salesforce-esignature.md).

- **1 min 8 s** from Send for Signature to Closed Won in a real-time demo with one signer (write-back on the Pro plan and up)
- **Free, MIT licensed**: the app, plus 5 signatures a month on the Free plan
- **Signed copy on the record**: on the Pro plan and up

## What do you need before you start?

- A Salesforce Enterprise, Unlimited, Performance or Developer Edition org, or a sandbox of one. Professional and Group editions are not supported.
- System Administrator access, or permission to install packages.
- A TurboDocx account. The Free plan works and includes 5 signatures a month.
- A TurboDocx template with a text token wherever someone signs or dates the contract.
- The Pro plan or higher if you want the signed copy saved back to the record and the stage updated.

No org to try it in? A free Salesforce Developer Edition org works. Steps 1 to 4 are a one-time admin job. Steps 5 to 8 are what a rep does on every deal, and step 9 happens on its own.

## Step 1: How do you install the e-signature app in Salesforce?

A Salesforce admin with the System Administrator profile opens the install link, logs in, selects Install for Admins Only, and clicks Install. It takes a few minutes.

Open the latest release notes on GitHub (https://github.com/TurboDocx/turbodocx-salesforce/releases/latest). They list the production or Developer Edition install link and the sandbox install link, so you can try it in a sandbox first. To confirm, open Setup, type Installed Packages in Quick Find, and look for TurboSign for Salesforce in the list.

Teams that review code first can deploy the MIT licensed [source from GitHub](https://github.com/TurboDocx/turbodocx-salesforce) with the Salesforce CLI instead. The [install guide](https://docs.turbodocx.com/docs/Integrations/turbosign-for-salesforce/install) covers both.

## Step 2: Which permission sets do reps and admins need?

Assign TurboSign Admin to the admins who build document setups and TurboSign User to the reps who send. Both include access to the TurboDocx credential.

In Setup, open Permission Sets, click TurboSign User, then Manage Assignments and Add Assignment. Any integration user whose Flows send documents needs TurboSign User too, or its sends fail with a credential error.

## Step 3: Where does the TurboDocx API key go in Salesforce?

Add your TurboDocx API key and Organization ID to the TurboDocxPrincipal principal on the TurboDocx API External Credential, as authentication parameters named ApiKey and OrgId.

Get both values in TurboDocx under Settings, then API keys. The key is shown once, when you create it, and the User access level is enough. In Salesforce, go to Setup, Named Credentials, the External Credentials tab, then TurboDocx API. In Principals, edit TurboDocxPrincipal, add the two parameters, and save.

- The names are case sensitive. A missing or misspelled one makes every send fail with Field TurboDocx_API.ApiKey does not exist.
- Salesforce encrypts both values, and nobody can view them after you save. They never sit in a field on a record or in a source file.

## Step 4: How do you set up a contract for e-signature in Salesforce?

On the TurboSign Setup tab, build a document setup: pick the TurboDocx template, map its values to opportunity fields, add the signers, and place the signing spots. Then add the Send for Signature button to the Opportunity page.

A document setup is one contract your reps can send, such as a service agreement, built in a no-code form:

- **Template.** Type a Label, leave Source Object as Opportunity, and choose your template under TurboDocx Template. If your templates show up, the connection works.
- **Data mapping.** Click Suggest fields, then check every guess. Map through relationships, such as Account and then Account Name. A Required value stops the send when it is empty.
- **Signers.** Under Recipients, pick the fields that hold each signer's name and email, such as the opportunity owner. Click Add recipient and check Fixed value for a countersigner who is not on the record. Drag rows to set the signing order.
- **Signing spots.** Your template needs a text token wherever someone signs or dates, such as `{sig}` and `{date}`. Set each token's Kind (such as Signature, Initial, Date or Text) and Recipient, then click Check anchors against template. Every token should say found in the document.
- **On Completion (optional).** Set field to Stage and To value to Closed Won to move the deal forward when everyone signs. This update is part of the write-back, which is on the Pro plan and up.
- **Test and save.** Pick a real record under Test with a record, click Preview values, then Save Configuration.

Last, add the Send for Signature action to the Opportunity page (see the first question in the FAQ below). Setups are custom metadata, so you can build one in a sandbox and deploy it to production. The [setup guide](https://docs.turbodocx.com/docs/Integrations/turbosign-for-salesforce/setup) has screenshots for every click.

## Step 5: How do you send a contract for signature from an opportunity?

On the opportunity, the rep clicks Send for Signature, picks the contract under Document, and clicks Review. TurboSign fills the document from the record.

The button sits at the top right of the record, or in the menu next to the other buttons when they don't all fit.

## Step 6: How do you check the contract values before it goes out?

The Details tab lists every value going into the document and the field it came from. The rep corrects anything that is off and checks each name and email under Signers.

A correction here changes only this send, not the Salesforce record.

## Step 7: Can you preview the document before sending it from Salesforce?

Yes. The Document tab shows the contract as it will go out, with the rep's corrections applied. It renders the first time the tab opens, which can take a minute or two.

- Signing spots look blank in the preview. Each signer gets a box there when the document goes out.
- After the render, Details says All signature spots found in the document, or names the token and signer that are missing.
- Change a value after the render and the tab shows Your edits aren't in this preview yet. Click Update preview to see it. Send always uses the latest values.

## Step 8: What happens after you click Send?

The rep clicks Send. Sent for signature appears once TurboDocx has accepted the document and emailed the first signer. Signers sign in order.

Each signer gets an email link once the person before them finishes, then signs in the browser or on their phone and clicks Submit Signature. The TurboSign Signatures panel on the record lets reps refresh the status, send a reminder, or void the document.

## Step 9: Where does the signed copy go?

On the Pro plan and up, when everyone has signed, TurboDocx saves the signed PDF and the Audit Trail PDF to the opportunity's Files and runs the On Completion update, such as Stage to Closed Won.

The write-back also needs version 1.1.0 or later of the app and the Salesforce connection in your TurboDocx settings, pointed at the same org. Sending works without it. The [Salesforce integration docs](https://docs.turbodocx.com/docs/Integrations/SalesForce#send-for-signature-with-turbosign-for-salesforce) cover the connection.

Saving can take a minute after the last signature. A voided or expired document saves nothing.

## How long does it take to get a contract signed from Salesforce?

In a real-time demo, it took 1 minute 8 seconds to go from clicking Send for Signature on an opportunity to the signed copy back on the record and the deal at Closed Won, with one signer. Saving the signed copy and updating the stage is on the Pro plan and up.

The one-time admin setup takes about 20 minutes after the install, per the [TurboSign for Salesforce setup guide](https://docs.turbodocx.com/docs/Integrations/turbosign-for-salesforce/setup).

## Can Salesforce send contracts for signature automatically?

Yes. The app includes a Flow action that runs the same send with no rep clicking the button, for example when an opportunity reaches a stage. Give the Flow's running user the TurboSign User permission set.

- [Send for signature automatically with Flow](https://www.turbodocx.com/guides/salesforce-flow-e-signature.md): send a contract when an opportunity reaches a stage.
- [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.
- [Salesforce proposal automation](https://www.turbodocx.com/resources/salesforce-proposal-automation.md): build the proposal from the same opportunity first.
- [Sales automation guide](https://www.turbodocx.com/resources/sales-automation-guide.md): where e-signature fits in the rest of the sales process.

## How much does it cost to send documents for signature from Salesforce?

The [e-signature app for Salesforce](https://www.turbodocx.com/integrations/salesforce-esignature.md) is free and MIT licensed. Signatures run on your [TurboSign](https://www.turbodocx.com/products/turbosign.md) plan:

| Plan | Sending from Salesforce |
|---|---|
| Free | Send from Salesforce with 5 signatures a month. The signed copy is not saved back to the record. |
| Pro | The app sends with your API key, so Salesforce sends count toward the 60 API signatures a month listed for Pro. The write-back is on the Pro plan and up. |
| Enterprise | Everything in Pro, with Salesforce signature volume set per contract and custom API limits. |

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. [Compare plans on the pricing page](https://www.turbodocx.com/pricing.md).

## Common questions about sending documents for signature from Salesforce

### Why don't reps see the Send for Signature button?

An admin has to add it to the Opportunity page. On a page with Dynamic Actions, add it to the Highlights Panel with Add Action. Otherwise, drag it into the Salesforce Mobile and Lightning Experience Actions section of the page layout, at the start of the list, because the page shows only the first few actions as buttons. Reps also need the TurboSign User permission set.

### Does editing a value in the send window change the Salesforce record?

No. A correction on the Details tab only affects that send. The opportunity keeps its original values, so fix the field on the record if the record itself is wrong.

### What happens if a required value is empty on the opportunity?

The send stops and tells the rep which value is missing. Fill in the field on the record and send again, or ask your admin to give that value a default or make it optional. A signer who is marked optional is skipped when their email field is empty.

### Can reps send documents for signature from the Salesforce mobile app?

Yes. Reps can review the values and send from their phone. The Document tab asks them to open the record on a computer to see the preview, but Send still works.

### How do signers verify their identity?

If your TurboDocx organization requires verification, each signer clicks Send code and enters a six-digit code sent to their email before they can sign. The Salesforce app does not send codes by text message, and because it sends no phone numbers, a send fails if your organization's default code method is text message. Every signer also agrees to sign electronically, and the Audit Trail PDF records who signed, when and from where.

Install free: https://github.com/TurboDocx/turbodocx-salesforce/releases/latest

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