n8n's new contract workflow goes from a spreadsheet row to a signed PDF, with a Slack approval click in between
The last manual step in most deal workflows is the signature, and n8n now has a verified node for it.
What happened
The n8n blog published a Verified Node Spotlight, written by TurboDocx CEO Nicolas Fry, that walks through a two part contract workflow. Part A runs every 15 minutes: it reads an Excel table, keeps rows marked Ready to send, generates each agreement from a Word template, and posts it to Slack with Approve & send and Reject buttons. Approved contracts go out for signature through the TurboDocx node, and the row flips to Sent or Rejected.
Part B starts when the client signs. A TurboDocx trigger downloads the executed PDF, uploads it to SharePoint, marks the row Signed and posts to Slack. Signature and date fields land on anchors in the template, so nobody drags fields into place. The post says Excel is only the queue: a CRM such as HubSpot, Pipedrive, Salesforce or Zoho CRM can replace it, and you can start on a deal moving to Closed Won instead of a schedule.
It lists limits too. The published template sends to one signer and does not handle redlines or negotiation. The TurboDocx free tier includes 5 generations and 5 signatures a month, and self hosted n8n needs a public HTTPS address for the signature webhook.
My take
This is the pattern I like for anything legal or financial: the template holds the clauses, the workflow only fills the blanks, and a person still clicks approve. That click is on record, which matters when a client asks who sent what.
If I were building this for a client, three changes:
- Trigger from the CRM stage, not a 15 minute poll, so the contract goes out while the deal is warm.
- Route by contract value, which the post also suggests, so big deals go to a senior approver.
- Write the signed date and document ID back to the deal record. The CRM should be the one place that shows where every contract stands.
Test it end to end with your own email as the signer before a real client ever sees it.
More posts
- Meta's Muse Ember costs $0.10 per million input tokens and targets the repetitive work agents do all dayNov 10, 2026
- Zapier's agent survey: 77% of firms with workflow-connected agents say they run mostly unattended, versus 8% withoutNov 10, 2026
- monday.com's AI revenue hit $36M ARR, mostly from credits bought on top of seats. Budget AI as a usage cost in every buildNov 10, 2026
