Salesforce e-signature in n8n
When a Salesforce opportunity reaches your contract stage, let n8n do the paperwork. The verified TurboDocx node generates the contract from your template, sends it for signature with TurboSign, and once it is signed, moves the opportunity to Closed Won with the executed PDF attached, no code and no per-seat e-signature add-on.
Verified by n8n on the official n8n integrations directory.
Sales reps live in the opportunity, and by the time a deal is ready to paper, everything the contract needs is already on the record: the account, the primary contact, the amount, the close date, and the products added during the cycle. The friction is what it takes to turn that into a signed contract. In most orgs it means a separate document-generation add-on plus a per-seat e-signature package bolted onto Salesforce, and a rep remembering to run both at the right moment.
This workflow keeps the trigger where the deal already changes: a stage move. When the opportunity reaches your contract or negotiation stage, n8n reads the record, generates the contract from your template, and sends it for signature, without a CPQ license or a signing seat for every rep. The document is built from the same fields your team already maintains, so nobody re-keys an account name or a line item into a Word file.
Because signing drives the close, the record stays honest. The opportunity flips to Closed Won only when the executed PDF actually comes back, and that PDF lands on the opportunity as an attachment automatically. No rep marks a deal won without a signed contract behind it, and no signed contract sits in an inbox instead of on the record.
The workflow, end to end
- 1A Salesforce opportunity moves into your contract stage, for example Negotiation or a Ready for Signature stage, and the Salesforce trigger starts the workflow.
- 2A Salesforce node reads the fields the contract needs: account, contact, close date, amount, and line items.
- 3The TurboDocx Generate Document operation merges those fields into your contract template and returns a finished DOCX or PDF.
- 4The TurboSign Send Signature operation emails the contract to the signer and starts tracking status.
- 5On the Document Signed event, a Salesforce node moves the opportunity to Closed Won and attaches the executed PDF that Download Document fetched.
Build it in four steps
Install the verified node
In n8n open Settings, then Community Nodes, click Install, and enter @turbodocx/n8n-nodes-turbodocx. It is verified for installation on n8n Cloud, so it installs directly with no self-hosting.
Trigger on your contract stage
Add a Salesforce trigger that fires when an opportunity reaches your contract or negotiation stage, then a Salesforce node to read the fields your contract needs.
Generate the contract
Add a TurboDocx node with the Generate Document operation, pick your template, and map the Salesforce fields to the template variables.
Sign, then close and file
Send the contract with TurboSign Send Signature. On the Document Signed trigger, move the opportunity to Closed Won and attach the executed PDF back to the record.
One node for generate, sign, and file
A signature-only tool still needs a separate document generator in front of it. The verified TurboDocx node generates the contract and collects the signature through a single credential, so the Salesforce flow stays one clean workflow instead of three stitched-together services.
- Generate the contract from your template, no manual editing.
- Send, track, remind, and download the signed PDF from the same node.
- Signing moves the opportunity to Closed Won and attaches the signed PDF automatically.
Frequently asked questions
How do I send a Salesforce contract for signature in n8n?
Use a Salesforce trigger in n8n to start the workflow when an opportunity reaches your contract or negotiation stage, before it is closed. A Salesforce node reads the record, the TurboDocx Generate Document operation builds the contract from your template, and the TurboSign Send Signature operation emails it to the signer. Every step is a drag-and-drop node, so no code is required.
Does the opportunity move to Closed Won and get the signed PDF automatically?
Yes. When the document is signed, the TurboDocx trigger fires a Document Signed event. Your workflow then moves the opportunity to Closed Won and uses the TurboSign Download Document operation to retrieve the executed PDF and attach it to the opportunity, so signing is what advances the deal and files the contract, with no manual step.
Do I need Salesforce CPQ or a paid e-signature add-on?
No. The workflow runs entirely in n8n with the verified TurboDocx node and your Salesforce connection. You do not need Salesforce CPQ or a per-seat e-signature add-on, because TurboDocx generates the document and TurboSign collects the signature through a single credential.
Is the TurboDocx n8n node verified for n8n Cloud?
Yes. TurboDocx publishes @turbodocx/n8n-nodes-turbodocx as a community node verified for installation on n8n Cloud. You install it from Settings, Community Nodes, with no self-hosting required, and it also runs on self-hosted n8n.
Which fields from Salesforce can I merge into the contract?
Any field you can read with the Salesforce node, such as account name, contact, close date, amount, and product line items, can be mapped to the variables in your TurboDocx template. Shape the data in n8n first with a Set or Code node if the template needs a specific structure.
Related
The full verified TurboDocx node: document generation, e-signature, quoting, and triggers.
Every TurboSign operation and signing trigger event the node exposes.
The same flow driven from a HubSpot deal instead of a Salesforce opportunity.
How the Generate Document operation turns template plus data into a finished file.
Automate Salesforce contracts in n8n
Install the verified TurboDocx node, connect Salesforce, and turn every contract-stage opportunity into a signed, Closed Won deal without leaving your workflow.
Get started free