---
title: "E-Signature for Salesforce: Free Open Source App | TurboDocx"
description: "E-signature for Salesforce: send contracts for signature from any record with a free, open source app. About half the price of big-brand e-signature."
url: "https://www.turbodocx.com/integrations/salesforce-esignature"
---

# E-signature for Salesforce

> Send contracts for signature from any Salesforce record. TurboSign for Salesforce adds a Send for Signature button and fills the document from the record. The app is free, and 5 signatures a month are free. On the Pro plan and up, the signed PDF and audit trail come back to the record and the stage updates when everyone signs.

Half the price compared with a typical big-brand e-signature plan at published list pricing (see the example under "How much can you save compared with big-brand e-signature?").

TurboSign for Salesforce is free and open source under the MIT license. Works on Enterprise, Unlimited, Performance and Developer editions.

- Install (production, Developer Edition and sandbox links in the latest release notes): https://github.com/TurboDocx/turbodocx-salesforce/releases/latest
- Setup guide: https://docs.turbodocx.com/docs/Integrations/SalesForce#send-for-signature-with-turbosign-for-salesforce
- Source: https://github.com/TurboDocx/turbodocx-salesforce

By the time a deal is ready to sign, the details the contract needs are already in Salesforce: the account, the contact, the amount, who owns the deal. TurboSign for Salesforce builds the document from those fields and sends it to the right people in the right order. On the Pro plan and up, it also puts the signed copy back on the record itself, where your team will look for it.

It is a Salesforce app your admin installs from one link. Documents come from a TurboDocx template, signatures run on TurboSign, and the app itself is free and open source.

Prefer n8n workflows? See [Salesforce e-signature workflows in n8n](https://www.turbodocx.com/integrations/n8n/salesforce-esignature.md).

## How do you send a document for signature from Salesforce?

Four steps from an open record to a signed document filed on it. A Flow action can run the same send automatically, for example when an Opportunity changes stage.

1. **Click Send for Signature on the record.** The app adds a Send for Signature button to Salesforce records, starting with Opportunity. The rep clicks it and picks the document setup they need, such as an order form or a lease.
2. **Review the values from the record.** The send window shows every value filled from the record, including related records such as Account.Name or Owner.Email. The rep edits anything that needs a change before it goes out.
3. **Preview the finished document, then send.** The rep sees the finished document inside the send window, with their edits applied, and sends it. Signers get it in order, verify by email code if required, and sign in the browser or on their phone.
4. **The signed copy lands on the record.** When everyone has signed, the signed PDF and the audit trail PDF are saved to the record's Files, and an optional field update runs, for example Stage to Closed Won. Saving the signed copy back and updating the stage is on the Pro plan and up.

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

## How do admins set up e-signature in Salesforce?

Each document your reps can send is a document setup, built in a no-code builder on the TurboSign Setup tab inside Salesforce. No code to write.

- **Template:** Choose the TurboDocx template the document is built from.
- **Data mapping:** Map each template value to a field on the record or a related record.
- **Signers:** Take signers from record fields or fixed values, set the signing order, and mark signers optional so they are skipped when their email is empty.
- **Signing spots:** Place the signing spots, and run the anchor check to confirm each one lands where it should in the document.
- **Test on a real record:** Run the setup against an actual record before your reps see it.
- **Deploy like the rest of your config:** Setups are custom metadata, so you build them in a sandbox and deploy them to production.

The admin guide (https://docs.turbodocx.com/docs/Integrations/SalesForce#send-for-signature-with-turbosign-for-salesforce) walks through building a setup, and the install guide (https://docs.turbodocx.com/docs/Integrations/turbosign-for-salesforce/install) covers installing the package and adding your TurboDocx API key and organization ID.

## Is e-signature in Salesforce secure?

- **Your API key stays out of fields and code.** The app calls TurboDocx through a Salesforce Named Credential, with the key encrypted on its External Credential. The TurboDocx API key and organization ID are never stored in a field on a record or in a source file.
- **Signers prove who they are.** Signers can verify their identity with a one-time code sent to their email, and each one consents to sign electronically before signing.
- **An audit trail on every signature.** Every signed document comes with an audit trail PDF, and the signed PDF is tamper-evident, so a change after signing shows.

Questions about security or volume? [Talk to our team](https://www.turbodocx.com/demo).

## Is there an open-source e-signature app for Salesforce?

The app is MIT licensed, written in Apex, Lightning Web Components (LWC) and one Visualforce page, and the full source is public. It ships as an unlocked package with no namespace. Read the code before you install it, deploy it from source with the Salesforce CLI, or fork it and change what you need: https://github.com/TurboDocx/turbodocx-salesforce

## How much does Salesforce e-signature cost?

The app is free on every plan, and 5 signatures a month are free. What changes is whether the signed copy comes back to the record, and how many signatures you can send from Salesforce. Saving the signed copy and updating the stage starts on the Pro plan.

| Plan | What you get with TurboSign for Salesforce |
|---|---|
| Free | Install the app and send from Salesforce records. 5 signatures a month. No write-back to the record. |
| Pro | Everything in Free. Salesforce sends count toward the 60 API signatures a month listed for Pro. Signed PDF and audit trail saved to the record's Files (Pro plan and up). Optional field update when everyone signs, such as Stage (Pro plan and up). Beyond 60 a month, API signatures start at $0.30 each, no minimums. |
| Enterprise | Everything in Pro. Salesforce signature volume set per contract. 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.

### How much can you save compared with big-brand e-signature?

Teams save 50% or more compared to leading e-signature providers' list prices. Take a typical team of 70 users: big-brand e-signature costs about $37,800 a year at published list pricing. TurboSign usually comes in at about half that, around $18,900 a year for the same team, with Salesforce included.

| | Price for 70 users |
|---|---|
| Typical big-brand e-signature plan | $37,800 a year (70 users × $45 per user per month, list price) |
| TurboSign, Salesforce included | about $18,900 a year (the same 70 users, usually half the price) |

Basis: example team of 70 users. Big-brand e-signature: 70 users × $45 per user per month at published list pricing, November 2026, which is $37,800 a year. TurboSign: about $18,900 a year for the same 70 users, because TurboSign usually costs about half of big-brand list pricing. Your price depends on your plan and volume. The TurboSign for Salesforce app is free; saving the signed copy back to the record is on the Pro plan and up.

Compare plans: [pricing](https://www.turbodocx.com/pricing.md).

## Salesforce e-signature FAQ

### Which TurboDocx plan do I need for TurboSign for Salesforce?

Every plan, including Free, can install the open source TurboSign for Salesforce app and send documents for signature from Salesforce records. Free includes 5 signatures a month. Saving the signed PDF and audit trail back to the record, and updating a field such as Stage when everyone signs, is on the Pro plan and up. The app sends with your API key, so Salesforce sends count toward your API signature allowance: 60 a month listed for Pro, and custom API limits on Enterprise. Beyond 60 a month, API signatures start at $0.30 each, no minimums.

### How much does TurboSign for Salesforce cost?

The app is free and open source under the MIT license, and 5 signatures a month are free. Saving the signed copy back to the record and updating the stage is on the Pro plan and up. Teams save 50% or more compared to leading e-signature providers' list prices. For example, a typical team of 70 users pays about $37,800 a year for big-brand e-signature at published list pricing (70 users × $45 per user per month, November 2026). TurboSign usually comes in at about half that, around $18,900 a year for the same team, with Salesforce included.

### How do I send Salesforce deals to e-signature automatically?

Use the Flow action the app includes. A Flow can send the document for signature with no rep clicking the button, for example when an Opportunity moves to a new stage.

### Can contracts fill in automatically from Salesforce opportunity data?

Yes. Each document setup maps template values to fields on the record or a related record, such as Account.Name or Owner.Email. When a rep clicks Send for Signature, the contract is filled from the opportunity, and the rep can review or correct any value before it goes out.

### Which Salesforce editions are supported?

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

### Is TurboSign for Salesforce really free and open source?

Yes. The app is free and open source under the MIT license, and the full source is on GitHub. An admin can install the released package from the install link, or a developer can deploy it from source with the Salesforce CLI and fork it. Signatures run on your TurboDocx plan, and the Free plan includes 5 a month.

### Where is my TurboDocx API key stored?

Encrypted in Salesforce. The app calls TurboDocx through a Salesforce Named Credential, with the key encrypted on its External Credential. Your TurboDocx API key and organization ID are never stored in a field on a record or in a source file.

### Can signers verify their identity?

Yes. Signers can confirm who they are with a one-time code before they sign, sent to their email, following your TurboDocx organization's verification setting. One-time codes by text message (SMS) are available on the Pro and Enterprise plans for documents sent from TurboDocx; the Salesforce app does not send SMS codes yet. Because the app sends no phone numbers, a Salesforce send fails if your organization's default code method is text message, so use email codes. Each signer consents to sign electronically, then signs in the browser on a computer or on their phone, and the audit trail records each signature.

### What happens if a field on the record is empty?

Before sending, the rep sees every value filled from the record in the send window and can fill in or correct anything, then preview the finished document. For signers, a signer marked optional is skipped when their email field is empty, and everyone else still signs in order.

### Can I deploy document setups between a sandbox and production?

Yes. Document setups are saved as custom metadata, so you can build and test a setup in a sandbox and deploy it to production the same way you move the rest of your Salesforce configuration.

## Related

- [How to send documents for signature from Salesforce](https://www.turbodocx.com/guides/send-documents-for-signature-from-salesforce.md): Step by step: install the app, build a document setup and send your first contract from an opportunity.
- [Send Salesforce deals for signature automatically with Flow](https://www.turbodocx.com/guides/salesforce-flow-e-signature.md): Add the Send for Signature action to a record-triggered Flow so contracts go out when a stage changes.
- [Auto-populate contracts from Salesforce opportunity data](https://www.turbodocx.com/resources/auto-populate-contracts-from-salesforce.md): Map Amount, Account and Owner fields into a contract and take signers straight from the record.
- [Salesforce e-signature workflows in n8n](https://www.turbodocx.com/integrations/n8n/salesforce-esignature.md): Prefer to build the flow yourself? Generate and send Salesforce contracts with the verified TurboDocx n8n node.
- [Salesforce proposal automation](https://www.turbodocx.com/resources/salesforce-proposal-automation.md): Generate proposals from Opportunity, Account and Contact records in TurboDocx.
- [TurboSign e-signature](https://www.turbodocx.com/products/turbosign.md): The e-signature product behind the app, with 5 free signatures every month.
- [E-signature identity verification](https://www.turbodocx.com/electronic-signature-identity-verification.md): How one-time codes confirm who a signer is before they sign.

## Get started

An admin installs the app from the install link, adds your TurboDocx API key and organization ID, and builds the first document setup. Every plan can start sending, including Free, with 5 signatures a month at no cost. [Install free](https://github.com/TurboDocx/turbodocx-salesforce/releases/latest) (production and sandbox install links are in the latest release notes) or [create a free TurboDocx account](https://app.turbodocx.com/signup?utm_source=website&utm_medium=integration&utm_campaign=salesforce-esignature).

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