Pipedrive e-signature in n8n
When a Pipedrive deal reaches a pre-close 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, marks the deal Won with the executed PDF attached, no code and no bolt-on e-signature add-on.
Verified by n8n on the official n8n integrations directory.
Pipedrive is built around the pipeline, and by the time a deal is ready to paper, the record already holds what the contract needs: the deal title and value, the linked person and organization, the products added during the cycle, and the activities that logged every touch. What Pipedrive does not have is a way to turn that record into a signed document. There is no native document generation and no native e-signature, so teams bolt on a separate document add-on and a per-seat signing package, then rely on a rep to remember to run both at the right stage.
This workflow keeps the trigger where the deal already changes: a stage move. When the deal reaches a pre-close stage such as Contract Sent or a negotiation stage, and not the Won stage, n8n reads the deal with its person, organization, and products, generates the contract from your template, and sends it for signature. Nobody re-keys an organization name or a product line into a Word file, because the document is built from the same fields your team already maintains in Pipedrive.
Because signing drives the win, the pipeline stays honest. The deal flips to Won only when the executed PDF actually comes back, and that PDF lands on the deal as an attachment automatically. The write-back is bound to the Document Completed event, not Document Signed, since Document Signed reports partial progress and does not fire on the final or single signature. No rep marks a deal Won without a signed contract behind it, and no signed contract sits in an inbox instead of on the deal.
The workflow, end to end
- 1A Pipedrive deal moves into a pre-close stage in your pipeline, for example a Contract Sent or negotiation stage rather than Won, and the Pipedrive trigger starts the workflow.
- 2A Pipedrive node reads the deal along with its linked person, organization, and products, so the contract has every value it needs.
- 3The TurboDocx Generate Document operation merges those values 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 Completed event, a Pipedrive node marks the deal Won and attaches the executed PDF that Download Document fetched. Use Document Completed here, because the Document Signed event reports partial progress and never fires on the final or single signature.
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 a pre-close stage
Add a Pipedrive trigger that fires when a deal reaches a pre-close stage such as Contract Sent or negotiation, then a Pipedrive node to read the deal, its person, organization, and products.
Generate the contract
Add a TurboDocx node with the Generate Document operation, pick your template, and map the Pipedrive deal, person, organization, and product fields to the template variables.
Sign, then win and file
Send the contract with TurboSign Send Signature. On the Document Completed trigger, mark the deal Won and attach the executed PDF back to the deal. Bind the write-back to Document Completed, not Document Signed, so it runs only once every party has signed.
One node for generate, sign, and file
A signature-only tool still needs a separate document generator in front of it, and Pipedrive gives you neither out of the box. The verified TurboDocx node generates the contract and collects the signature through a single credential, so the Pipedrive 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.
- The Document Completed event marks the deal Won and attaches the signed PDF automatically.
Frequently asked questions
How do I send a Pipedrive deal contract for signature in n8n?
Use a Pipedrive trigger in n8n to start the workflow when a deal reaches a pre-close stage such as Contract Sent or negotiation, before it is marked Won. A Pipedrive node reads the deal with its linked person, organization, and products, 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 deal move to Won and get the signed PDF automatically?
Yes. When every party has signed, the TurboDocx trigger fires a Document Completed event. Your workflow then marks the deal Won and uses the TurboSign Download Document operation to retrieve the executed PDF and attach it to the deal, so signing is what advances the deal and files the contract, with no manual step.
Do I need a Pipedrive e-signature or document generation add-on?
No. Pipedrive has no native document generation or e-signature, so teams normally bolt on a separate document add-on plus a per-seat signing package. This workflow runs entirely in n8n with the verified TurboDocx node and your Pipedrive connection, because TurboDocx generates the document and TurboSign collects the signature through a single credential.
Why does the write-back use the Document Completed trigger instead of Document Signed?
The Document Signed event reports partial progress and never fires on the final or single signature, so it is not a reliable signal that the contract is fully executed. The Document Completed event fires only when every party has signed, which is why the deal is marked Won and the executed PDF is attached on Document Completed rather than Document Signed.
Which Pipedrive fields can I merge into the contract?
Any field you can read with the Pipedrive node, such as the deal title and value, the linked person and organization, and the products attached to the deal, 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 Salesforce opportunity instead of a Pipedrive deal.
How the Document Completed and other trigger events drive the write-back step.
Automate Pipedrive contracts in n8n
Install the verified TurboDocx node, connect Pipedrive, and turn every pre-close deal into a signed, Won deal without leaving your workflow.
Get started free