Skip to main content

TurboSign for Salesforce

TurboSign for Salesforce lets your team send a TurboDocx document for e-signature straight from a Salesforce record. The document fills itself from the record's fields, the signers come from the record, and when everyone has signed, the signed PDF and its audit trail are saved back to the record. The record can also move to a new stage automatically, for example Closed Won.

How it works​

  1. An admin builds a document setup once: which TurboDocx template to use, which Salesforce fields fill it, who signs, and where each person signs.
  2. A sales rep opens a record, clicks Send for Signature, reviews the filled-in values and the finished document, and clicks Send.
  3. Each signer gets an email, verifies their identity if your organization requires it, and signs in the browser.
  4. When the last signer finishes, TurboDocx writes the signed PDF and the audit trail to the record's files and updates the stage you chose.

Your TurboDocx API key never sits in a Salesforce field. It is stored encrypted in a Salesforce External Credential and added to each request by Salesforce itself, so nobody can read it back from Setup.

Guides​

If you want to…Read
Install the package in your Salesforce orgInstall TurboSign for Salesforce
Find the install link for your org type, or check your installed versionOne-click install links
Set everything up in Salesforce Setup, click by clickSet up TurboSign for Salesforce
Send a document and see what signers experienceSend a document for signature
Configure it from the Salesforce CLI after installingScripted setup for admins
Fix an error messageTroubleshooting

What you need​

  • A Salesforce org where you are a System Administrator, on an edition that can run it. See Which Salesforce orgs can use it.
  • A TurboDocx account with TurboSign, plus an API key and your Organization ID. See Getting your credentials.
  • A TurboDocx template. Every spot where someone signs must already be in the template as a text token, for example {sig}.
  • The Salesforce integration connected in TurboDocx. Saving signed files back to Salesforce depends on TurboDocx's Salesforce write-back feature, which is part of TurboDocx and uses that connection to save the signed PDF to the record. The Salesforce integration is included on the TurboDocx Pro and Enterprise plans. Sending for signature works without it.

Which Salesforce orgs can use it​

Your Salesforce edition decides whether TurboSign for Salesforce can run in your org. The install method decides who puts it there.

TurboSign for Salesforce includes custom Apex code, so it needs an edition that runs custom Apex.

Salesforce editionCan use TurboSign for Salesforce
EnterpriseYes
UnlimitedYes
PerformanceYes
Developer EditionYes
Sandboxes of the editions aboveYes
ProfessionalNo
GroupNo
Starter, Pro Suite, EssentialsNot supported

Professional and Group editions block custom Apex unless it ships in a managed package that passed the Salesforce AppExchange security review. TurboSign for Salesforce is not offered that way today. If you are on Starter, Pro Suite, or Essentials, or you are not sure which edition you have, check with your Salesforce account rep.

How it gets installed​

MethodWho can do itUpgrades and removal
One-click install linkAny Salesforce admin in your org, by clicking the linkA new version installs over the old one. Uninstall in one click.
Deploy from source with the Salesforce CLIA developer, using sf project deploy startManual. Deploying to production runs your org's Apex tests, which must reach 75% code coverage.

There are two ways to install, and step-by-step instructions for both are in Install TurboSign for Salesforce. The method doesn't change which orgs can run TurboSign for Salesforce. It changes whether your own admin can install it, or whether someone has to deploy it for you. Either way, the person installing needs permission to install packages, which the System Administrator profile has.