Fill legal intake documents from form data with DocuSign, Google Drive and email
Ready for 3.0What this workflow does
This workflow has 22 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Google Drive.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Validate And Normalize Intake Data (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Build Document Fill List (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Split Into Single Document Items (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Fetch DocuSign User Info (HTTP Request): calls an HTTP API (GET)
- Copy Google Docs Template (Google Drive): copy (file)
- Build DocuSign Envelope Request (Code): runs custom JavaScript code
- Build Google Docs Merge Requests (Code): runs custom JavaScript code
…plus 9 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - HTTP Request
n8n-nodes-base.httpRequest - Google Drive
n8n-nodes-base.googleDrive - Merge
n8n-nodes-base.merge - Execute Sub-workflow
n8n-nodes-base.executeWorkflow - Send Email
n8n-nodes-base.emailSend
From the author
Quick Overview This workflow receives intake form submissions via webhook, validates required fields, generates practice-area-specific documents by merging data into Google Docs templates or creating DocuSign draft envelopes, then aggregates results, logs an…