Salesforce and DocuSign: Sending Contracts Without Leaving the Opportunity
A managed package that pulls Salesforce data into an envelope and writes the signed result back. Straightforward to install, and the field merge is where the actual project lives.
- Connector
- Native — DocuSign eSignature for Salesforce managed package from the AppExchange
- Sync direction
- Salesforce → DocuSign for envelope data; DocuSign → Salesforce for status and completed documents
- Setup time
- A few hours for basic sending; days to weeks with document generation and templates
- Availability
- Requires a DocuSign plan that includes the Salesforce integration; DocuSign Gen for document generation is a separate product
| What | Direction | Detail |
|---|---|---|
| Envelope creation | Salesforce → DocuSign | Launched from an opportunity, account, contract or custom object, with the recipient list pre-populated from related contacts. |
| Merge fields | Salesforce → DocuSign | Salesforce field values populate document tags — names, amounts, dates, terms. Configured per template and the main source of setup effort. |
| Envelope status | DocuSign → Salesforce | Sent, delivered, viewed, signed, completed, declined and voided all write back to the record in near real time. |
| Completed document | DocuSign → Salesforce | The executed PDF attaches to the Salesforce record, so the contract lives with the opportunity rather than in someone's inbox. |
| Signer data writeback | DocuSign → Salesforce | Values a signer typed into the envelope can map back onto Salesforce fields — useful for capturing a PO number or a start date at signature. |
| Status-driven automation | DocuSign → Salesforce | Completed envelopes can trigger Flow — move the opportunity to closed-won, create the onboarding record, notify finance. |
Setting it up
- Confirm which DocuSign products you actually have — eSignature for Salesforce and DocuSign Gen are different line items, and the plan you need depends on whether you are generating documents or only sending them.
- Install the managed package in a sandbox and test against real opportunity data, including a multi-line deal and a multi-signer scenario.
- Build one template properly before building five. Anchor tags, merge fields and signing order all have edge cases that only appear on real documents.
- Map the writeback fields deliberately: envelope status, completed date, and any signer-entered values you want on the record.
- Assign permission sets to the sending group, and confirm document visibility follows your record sharing model rather than exposing contracts more widely than intended.
- Build the post-signature Flow — stage change, notification, onboarding record creation — because the automation after completion is where most of the time saving actually comes from.
- Set a sandbox test as part of your release process for managed package upgrades. Envelope failures are customer-visible.
Where the integration stops
- Document generation is a separate product. The eSignature package sends and tracks; building the contract itself from Salesforce data is DocuSign Gen, licensed separately. Teams routinely conflate the two when budgeting.
- Managed package upgrades are real maintenance. Version updates need testing in sandbox, particularly where custom objects and Flows depend on envelope status fields.
- Template and tag configuration is fiddly. Anchor tags shifting when a document is edited is the most common cause of a broken send, and the failure surfaces to the customer rather than internally.
- Recipient routing complexity lives in DocuSign, not Salesforce. Multi-party signing orders, counter-signing and conditional routing are configured on the DocuSign side, which splits the process across two admin surfaces.
- Licensing counts senders. Every rep who sends needs an entitlement, which is a per-seat cost separate from Salesforce.
Why this integration is usually worth doing
Contract sending is one of the few sales workflows where the manual version has a measurable cost. Rekeying names, amounts and dates from an opportunity into a document is slow and produces errors that land in front of a customer at the worst possible moment.
Pulling those values from the record removes an entire class of embarrassment, and the status writeback removes the daily "has it been signed yet" question.
The part people underestimate
Template configuration. The install is genuinely easy — a managed package, some permission sets, a connection. What takes the time is getting one document to merge correctly, route to the right signers in the right order, and write the right values back.
Budget for one template done properly rather than five done approximately. The second template takes a fraction of the time once the patterns are established.
The automation that pays for it
Envelope completed is the highest-quality trigger in a sales process. It is unambiguous, it is timestamped, and it means something specific happened.
Wire it to the things that should happen next: stage change, finance notification, onboarding record creation, provisioning request. Teams that stop at "the PDF is on the record" get half the value; teams that treat completion as the start of an automated handoff get the rest.