Send TurboDocx e-signature contracts from Excel with Slack approval and SharePoint filing
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 16 nodes and runs on a schedule (every 15 minutes) (plus 1 other trigger). Along the way it connects Microsoft Excel 365, Slack, Microsoft SharePoint and Turbodocx (community).
How it runs
Trigger: On a schedule (every 15 minutes) (plus 1 other trigger).
- Fetch Contracts from Excel (Microsoft Excel 365): lookup (table)
- Fetch Signed Contract PDF (Turbo Docx): download document (turbo sign)
- Loop Over Contracts (Loop Over Items (Split in Batches)): loops over the items in batches
- Store PDF in SharePoint (Microsoft SharePoint): upload (file)
- Generate Agreement Docx (Turbo Docx): generate (deliverable)
- Update Signed Status in Excel (Microsoft Excel 365): create or update (worksheet)
- Request Slack Approval (Slack): send and wait for a reply (message)
- Notify Slack of Signed Contract (Slack): uses Slack
- If: checks a condition and branches into true / false
- Convert Agreement to PDF (Turbo Docx): download pdf (deliverable)
…plus 4 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 2 community packages, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @turbodocx/n8n-nodes-turbodocx is verified or supports 3.0 (used in Generate Agreement Docx, Convert Agreement to PDF, Send Agreement for E-Signature).
- Check that @turbodocx/n8n-nodes-turbodocx is verified or supports 3.0 (used in When Contract Signed).
Nodes used (8)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Microsoft Excel 365
n8n-nodes-base.microsoftExcel - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Turbo Docx
@turbodocx/n8n-nodes-turbodocx.turboDocx - Slack
n8n-nodes-base.slack - If
n8n-nodes-base.if - Turbo Docx Trigger
@turbodocx/n8n-nodes-turbodocx.turboDocxTrigger - Microsoft SharePoint
n8n-nodes-base.microsoftSharePoint
From the author
Quick overview Rows in an Excel table (in SharePoint) are the queue. For each contract marked Ready to send, TurboDocx generates the agreement, a manager approves it in Slack, then it is sent for e-signature. When signed, the PDF is filed to SharePoint and…