Salesforce and DocuSign integration
Agreements go out from the deal with the right template and signers, and signed terms, dates and signers come back onto it every time.
Both waysSalesforce and DocuSign
What moves between them
- Into SalesforceCompletion status, the signed date, who signed and merged field values from the signed document, written back by DocuSign Connect.
- Out of SalesforceAgreements generated from deal data with the right template, region and countersigner, sent by the people allowed to send them.
How we build it
- Templates generated from the dealTerms, pricing and dates come from Salesforce fields, so nobody retypes a contract.
- Signer routing by ruleSigners and countersigners chosen by region and deal type, with the send button shown only when the deal is ready.
- Writeback mapped and permittedEvery field the signed document writes back is mapped, and every sender can edit it. The writeback runs as the sender, not as an integration user.
- A daily reconciliationCompleted envelopes compared with deal status each morning, and the owner told the same day when one did not land.
What goes wrong, and the fix
Problems we have found and fixed in production.
- Signed in DocuSign, still “Sent” in SalesforceUsually a sender without edit access to a writeback field, a validation rule on stage, or a trigger failing downstream. The package logs each one. Our guide walks through all five causes.
- Deals skip straight past the signed stage, or not at allStage rules written for reps also stop the automation. The signature path gets its own exemption.
- “You do not have access to this envelope”Often a user consent or app permission in DocuSign rather than a Salesforce sharing problem. We check both sides before changing anything.
Guides
- Why a completed DocuSign envelope never reaches SalesforceThe signer finished, DocuSign shows Completed, and the Salesforce record still says Sent. In the orgs we work on it is almost always one of five causes, and the package logs every one of them.
Questions
Which DocuSign package do we have?
Current orgs use DocuSign eSignature for Salesforce, whose objects start with dfsle. Many older orgs also still have the legacy package installed, whose objects start with dsfs. Flows and reports should read the current one.
Can we tell when a writeback failed?
Yes. The package records each failure in its log object with the original error. We add a daily check so nobody has to look.
Other Salesforce integrations
- Salesforce and SnowflakeWarehouse metrics on every Salesforce account, Salesforce data in the warehouse for reporting, and one definition both sides agree on.
- Salesforce and Adobe Commerce (Magento)Customers, orders and catalogue kept in step between Salesforce and the storefront, with one ID both sides trust and a switch in front of every write.
- Salesforce and commercetoolsA move to commercetools without splitting customers in two: the same account IDs on the new platform, orders from both platforms counted once, and the old platform retired in planned steps.
- Salesforce and Microsoft Dynamics 365Closed deals become billing records in Dynamics 365 with the right product codes and dates, and billing status comes back to the account.
- Salesforce and Apollo.ioProspects and enrichment from Apollo.io without blanked fields, wrong owners or “new” leads that are already customers.
- Salesforce and IntercomSupport chats logged on the right contact and account, credited to the person who answered, and the account owner and region visible to the support team.
Talk to us about Salesforce and DocuSign.
Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.