Home / News

n8n can now send contracts for e-signature via a verified TurboDocx node

An n8n developer can now build a complete contract-to-signature workflow for a small business in a few days. The missing step was the e-signature itself, and it now has a verified TurboDocx node: data in, contract generated, approved in Slack, signed and filed with no manual handoffs.

A guest post on the n8n Blog by TurboDocx CEO Nicolas Fry walks through the build. An Excel row marked Ready to send becomes a PDF contract built from a Word template. A manager approves it in Slack and the client gets it to sign. The signed copy then lands in SharePoint and the row updates itself. You can swap Excel for a CRM, Slack for Teams, or SharePoint for Google Drive.

What this means for a small business

The win is simple. Contracts stop sitting in an inbox for three days, and signed PDFs stop disappearing into Downloads folders. The limits are concrete too. The free tier covers 5 documents and 5 signatures a month, and the template checks for new contracts every 15 minutes unless a CRM deal stage triggers it. The workflow has no AI. I would add a Claude step before approval to compare deal data against the template and flag odd amounts or dates, like the risk checks in an AI legal assistant I built. Under strict data rules, also check where TurboDocx stores signer data.

Why it matters: If your contracts already follow one approved template, automating them takes about a week. Start with the template and a status column, and add AI review only where someone currently rereads every contract by hand.

Source: n8n Blog