Private app on requestCRM
Salesforce logo

Choosing a Docusign Salesforce integration

Docusign publishes several Docusign Salesforce integrations, which send envelopes from records and write signed data back, and Salesforce builds Docusign e-signature into Salesforce Contracts. Fluidlabs builds a private app for your account when that data must reach your ERP.

Docusign publishes and supports eSignature for Salesforce and Gen for Salesforce on Salesforce AgentExchange, and the Salesforce app on the Docusign App Center. Salesforce builds Docusign e-signature into Salesforce Contracts. Fluidlabs built none of them.

Docusign + SalesforceWhat should Salesforce and Docusign do together?An engineer replies within 48 hours with a scoped plan and a fixed price.

Used to reply to you about this request. Nothing else.

Status
Private app on request
Public integrations
By Docusign and Salesforce
Private app hosting
US, EU or both
Fluidlabs security
ISO 27001, GDPR, SOC 2 Type II audit in progress

Which Salesforce Docusign integration fits your process?

Docusign publishes several apps for Salesforce, and Salesforce builds e-signature into its own contract product. Most teams can start with one of these. The routes differ in where the agreement starts and in what returns to Salesforce.

The line above each card names who publishes that route. Fluidlabs publishes none of the public routes. The last card is the private app we build for one customer.

Published by Salesforce

Salesforce Contracts e-signature

Salesforce builds Docusign e-signature into Salesforce Contracts. A user sends a contract document for review and signature, and Salesforce tracks the signed document and updates the contract record status. E-signature APIs send documents that Salesforce generates from quotes, orders and opportunities. It needs an active Docusign account and a Contract Management or DocGen permission set license.

Choose it when your contracts live in Salesforce Contracts and the signature is one step of that contract lifecycle.

Published by Docusign

Salesforce apps from Docusign

Docusign publishes several apps. eSignature for Salesforce sends envelopes from records and flows and writes signed data back. Gen for Salesforce generates the document from Salesforce data, quotes from Salesforce CPQ included. The Salesforce app from Docusign on the App Center adds read, writeback and file steps to Docusign Workflow Builder, and a Salesforce flow starts the workflow.

Choose it when the agreement starts from a Salesforce record or flow and the signed data returns to Salesforce.

Published by Zapier, Make and NeuraFlash

Connectors (Zapier, Make, MuleSoft)

Zapier and Make each list Docusign and Salesforce. Each automation runs inside the connector, and your team keeps it working. For MuleSoft, NeuraFlash publishes the MuleSoft Accelerator app on the Docusign App Center.

Choose it when a single automation covers the need and your team runs that connector today.

Built by Fluidlabs for you

A private app for your account

The Docusign apps connect Salesforce and Docusign. Your private app adds the work between Salesforce, Docusign and a third system such as your ERP. It maps signed terms between their record models, retries a write a system rejects, and files signed documents larger than the 10 MB the Docusign Store Files step takes. We build it for your account alone, publish it to your Docusign accounts only and host it.

Choose it when the agreement process reaches a third system, such as your ERP, and you want us to run the mapping, retries and monitoring between the systems.

Salesforce Contracts e-signatureSalesforce apps from DocusignConnectors (Zapier, Make, MuleSoft)A private app for your account
Who publishes itSalesforceDocusignZapier and Make. NeuraFlash publishes the MuleSoft Accelerator appFluidlabs builds it for your account
Where it startsInside Salesforce Contracts, from a contract documentFrom a Salesforce record or flow, or from a Workflow Builder start methodIn the connector, from a trigger on either productFrom the Salesforce event you name, through the Docusign flow action or the API
Reads Salesforce data into the agreementSalesforce generates the document from the contract, quote, order or opportunityYes, through merge fields, Gen templates and the Read from Salesforce stepDepends on the connector's actionsYes, through the Docusign Read step or a query on Salesforce's API
Writes signed values back to SalesforceSalesforce updates the contract record status. Field write-back: Not stated in Salesforce's documentationYes, through writeback in eSignature for Salesforce and the Writeback to Salesforce stepDepends on the connector's actionsYes, through the Docusign Writeback step or Salesforce's API
Stores the signed document in SalesforceSalesforce tracks the signed contract documentYes. eSignature for Salesforce saves signed documents to the record, and the Store Files step takes files up to 10 MBDepends on the connector's actionsYes, as a Salesforce file linked to the record you name
Starts from a Salesforce eventNot stated in Salesforce's documentationYes. A flow sends an envelope or starts a Docusign workflowYes, from a trigger in the connectorYes, from a flow, a change event or a platform event
Salesforce CPQ quotesNot stated in Salesforce's documentationGen for Salesforce lists an integration with Salesforce CPQNot stated on the connector pagesYes, through Salesforce's API, which reads standard and custom objects
What it needsAn active Docusign account and a Contract Management or DocGen permission set licenseeSignature for Salesforce has paid plans. The Docusign App Center app needs an IAM plan. Its install guide names IAM for SalesA connector accountA written scope with a fixed price, then a monthly hosting plan

Verified on 27 September 2026. The last column describes what a private app can do once we confirm it against your accounts during scoping.

What each Docusign and Salesforce integration covers

Each note below comes from the publisher's own documentation, in its terms. Docusign lists its App Center app under the name Salesforce, so the first five notes carry that name.

  1. A read returns up to five records

    App from Docusign, listed as Salesforce

    A Read from Salesforce step returns up to five records that match your rule. With more matches, Salesforce logic decides which five the step returns.

  2. Store Files takes files up to 10 MB

    App from Docusign, listed as Salesforce

    The Store Files in Salesforce step stores files up to 10 MB. It needs a Read from Salesforce or Writeback to Salesforce step before it in the workflow.

  3. A flow passes ten text variables

    App from Docusign, listed as Salesforce

    A Salesforce flow hands the workflow up to ten variables of the Text type: Record ID and Variable 1 to Variable 9.

  4. Workflow progress stays in Docusign

    App from Docusign, listed as Salesforce

    Standard Salesforce users cannot view the progress of a Docusign workflow in Salesforce. Salesforce administrators see failed starts in the Docusign Logs tab, and Docusign administrators monitor the workflows in Docusign.

  5. Templates take merge fields from one object

    App from Docusign, listed as Salesforce

    Workflow Builder uses envelope templates whose Salesforce merge fields come from a single source object, such as Opportunity. A template with fields from more than one object returns an error.

  6. Data writeback covers two field types

    App from Docusign, listed as Docusign eSignature for Salesforce

    Data writeback works for text fields and picklist fields. Writeback fails for a Salesforce user who has Multi-Factor Authentication for API Logins on.

  7. Up to 25 envelope events per template

    App from Docusign, listed as Docusign eSignature for Salesforce

    An envelope template holds up to 25 envelope events, five for each event type. Docusign cannot check the fields they update against Salesforce validation rules, so an update that breaks a rule fails.

  8. Envelope status arrives by polling

    Salesforce's integration, listed as Salesforce Contracts e-signature

    Salesforce Contracts polls Docusign for envelope status through a scheduled Apex class. Salesforce documents a minimum of 15 minutes between polls, and a job scheduled from the Salesforce UI runs once an hour.

What a private app covers

The apps from Docusign read, write and file Salesforce records. A private app covers work between the systems, such as the four jobs below. Each job rests on an ability that Salesforce or Docusign documents, and we confirm it against your Salesforce org during scoping.

Map signed terms between Salesforce and your ERP

Docusign Connect publishes an event when a workflow completes. Your private app maps the signed values to the opportunity through Salesforce's REST API and to the matching record in your ERP, and retries a write that either system rejects.

Read every line on the quote

The private app runs a SOQL query through Salesforce's API and passes every line of the quote to the workflow. The Docusign Read from Salesforce step still reads the opportunity and the contact.

File large signed documents on the record

eSignature for Salesforce saves signed documents to the record, and the Docusign Store Files step takes up to 10 MB. For a larger file, your private app uploads a ContentVersion up to 2 GB and links it to the record.

Show workflow status, failures included, on the record

Docusign Connect publishes an event when a workflow starts, fails or completes. The private app writes each status to a field on the opportunity, so a sales user sees it on the record without opening Docusign.

Salesforce's API, as we design around it

We took each fact from the vendors' own documentation and listings. The sources list at the foot of this page links each one.

Verified on 27 September 2026.

Authentication
A client application reaches the REST API through an external client app or a connected app and an OAuth 2.0 authorization flow. Salesforce restricts the creation of new connected apps as of Spring '26 and recommends external client apps.
Webhooks
Salesforce publishes change events and platform events. Change Data Capture publishes change events for record creates, updates, deletes and undeletes, and an external client receives events through Pub/Sub API or CometD. A flow calls an external API through the HTTP Callout action.
API limits
Salesforce allocates API requests per org for each 24-hour period. An Enterprise Edition org gets 100,000 requests plus 1,000 for each Salesforce license, and Unlimited and Performance Edition orgs get 100,000 plus 5,000 for each Salesforce license. A production org or a sandbox runs up to 25 concurrent requests that last 20 seconds or longer.
Test environment
Salesforce recommends an isolated environment for development and testing: a Developer Edition org, a sandbox or a scratch org. A Developer Edition org gets 15,000 API requests for each 24-hour period.
Marketplace listing
Salesforce AgentExchange. Salesforce renamed AppExchange to AgentExchange. A managed package or a Salesforce Platform API solution must pass Salesforce's security review before it goes on AgentExchange. A new solution must be Lightning Ready, and its publisher enrolls it in the ISV Partner Program.
API styles
REST, SOAP, Bulk API, Pub/Sub API
How a build runs

From the first call to a hosted integration

  1. Scoping call

    Thirty minutes with the engineers. We map the records, the direction of travel and the edge cases.

  2. Written scope

    You get a fixed scope and a fixed price in one document. It quotes hosting and maintenance too.

  3. Build and review

    We build against test accounts. We walk you through the result before anything touches production.

  4. Hosted and monitored

    We run your private app on infrastructure we operate. We version each deploy, so we can roll one back.

What revenue teams run on Salesforce and Docusign

Send the order form when an opportunity reaches Negotiation/Review

A record-triggered flow starts the Docusign workflow through the Docusign flow action. The Docusign Read from Salesforce step pulls the amount and the contact into the order form, and the rep stays in Salesforce.

Write the contract term and start date to the opportunity

The signer confirms the contract term on the agreement. The Docusign Writeback to Salesforce step puts the term and the start date on the opportunity, so you build the renewal report in Salesforce without retyping them.

Create the sales order in the ERP when the customer signs

Your private app updates the opportunity and creates the sales order in your ERP with the same values. Finance invoices from the order without asking sales for the signed terms.

Security & compliance

Built to pass your security review

The documents your security team will ask for exist, are current, and are ready to hand over. Terms of service and the privacy policy are published on this site.

ISO/IEC 27001:2022
Certified
SOC 2
In progress

EUR 1M technology and cyber insurance, evidenced on request.

Certification

ISO/IEC 27001:2022 certificate

Independently certified by Swiss Approval, current to May 2027 and verifiable through the issuing body.

Download the certificate (PDF)
Data processing

Standard DPA

GDPR, UK GDPR and Swiss FADP covered, with the EU standard contractual clauses incorporated. Read it now, request the version for signature.

Download the DPA (PDF)
Terms

Service Terms

Licence, support response targets, availability, IP and liability for your use of the extension apps. Personal data stays with the DPA.

Download the Service Terms (PDF)
Security overview

Security & Data Protection Overview

Certifications, hosting and encryption, access control, secure development, monitoring and incident response, in one document for your security assessment.

The Security & Data Protection Overview and the DPA prepared for signature are provided on request: , or email secops@fluidlabs.com.

FAQ

Salesforce and Docusign, answered

Does Salesforce integrate with Docusign?
Yes. Docusign publishes eSignature for Salesforce and Gen for Salesforce on Salesforce AgentExchange, the marketplace that Salesforce used to call AppExchange. The CLM and Agentforce apps from Docusign sit on the same marketplace. The Salesforce app from Docusign on the Docusign App Center adds read, writeback and file steps to Docusign Workflow Builder. Salesforce builds Docusign e-signature into Salesforce Contracts.
Does Fluidlabs have a Salesforce app on the Docusign App Center?
No. Docusign publishes and supports the Salesforce app on the Docusign App Center. For work between systems, such as mapping signed terms into your ERP, we build a private app for your account. We publish it so that only your Docusign accounts can install it, and we host it. If the apps from Docusign cover your process, use them. We can set them up in your account.
Can a Salesforce opportunity stage start a Docusign workflow?
Yes, and Docusign documents the steps. You add the Start Docusign Workflow action to a record-triggered flow, and the flow starts the workflow when the stage changes. You need a Docusign IAM plan, the Salesforce app that Docusign publishes on the App Center and Docusign Apps Launcher version 7.4 or higher. The flow passes up to ten text variables, such as the record ID.
How does a Salesforce CPQ Docusign integration work today?
Salesforce's retirement notice states that the older Docusign for Salesforce CPQ package stopped working after 31 January 2022, and it names two replacements from Docusign: eSignature for Salesforce and Gen for Salesforce. The Docusign Gen listing names an integration with Salesforce CPQ, and Salesforce documents Gen as an optional package for Salesforce CPQ Plus. Salesforce sends support requests for both packages to Docusign Support.
Do I need Zapier or Make for a Docusign integration with Salesforce?
No. The apps from Docusign cover sends, write-back and workflow starts, so you can run Salesforce and Docusign without a connector. Zapier and Make both list Docusign and Salesforce. A connector fits a single automation that your team wants to own.
Can a Docusign workflow call another system's API without a custom build?
Yes, when the other system's API fits the step. On qualifying IAM plans, such as IAM Professional and above, Docusign Workflow Builder has a Make a Web Request step, and Docusign installs the HTTP app the step needs. The step sends GET, POST or PUT requests to another system's API. The Docusign guide "Configure a Make a Web Request Step" lists Basic Auth connections, and the Docusign overview, "Connect to Any Service Using Web Requests", also lists OAuth 2.0 client credentials. If your system's API accepts one of those connections and each call is one of those requests, a workflow can call it. We check that on the scoping call. A custom build covers other sign-in methods and request types, and work that runs outside a workflow.
How does Fluidlabs price a custom integration?
We agree a fixed price in a written scope before work starts, then a monthly hosting plan. You see both numbers in the same document. Nothing bills hourly.
Who hosts and maintains what Fluidlabs builds?
Fluidlabs does. The engineers who build a private app or integration run it, monitor it and patch it. You choose the US region, the EU region or both, and your data stays there. Docusign and the other publishers on this page run and support their own public apps. The security and compliance section on this page has our certificate and agreements to download, and a form to request our security overview.

Related pages

Docusign + Salesforce

Scope your Salesforce and Docusign integration

Thirty minutes with an engineer, then a written scope with a fixed price.

Opens a short form here. You stay on this page.

Sources (59)

Each vendor fact on this page comes from one of the pages below.

Salesforce and the other product names and logos on this page are trademarks of their owners. Fluidlabs uses them to identify the products. Their use implies no endorsement. Docusign is a trademark of Docusign, Inc. To ask us to remove a mark, email hello@fluidlabs.com.