Run legal conflict checks with Clio, Google Sheets, and email
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 23 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects Google Sheets.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Parse Conflict Check Names (Code): runs custom JavaScript code
- Parse Conflict Decision Request (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- If: checks a condition and branches into true / false
- Fetch All Contacts From Clio (HTTP Request): calls an HTTP API (GET)
- Respond Invalid Conflict Request (Respond to Webhook): sends the response back to the webhook caller
- Read Conflict Check Audit Log (Google Sheets): read
- Respond Invalid Conflict Decision (Respond to Webhook): sends the response back to the webhook caller
- Fetch All Matters From Clio (HTTP Request): calls an HTTP API (GET)
- Find Matching Audit Log Row (Code): runs custom JavaScript code
…plus 11 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 (8)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Respond to Webhook
n8n-nodes-base.respondToWebhook - HTTP Request
n8n-nodes-base.httpRequest - Google Sheets
n8n-nodes-base.googleSheets - Execute Sub-workflow
n8n-nodes-base.executeWorkflow - Send Email
n8n-nodes-base.emailSend
From the author
Quick Overview This workflow runs two webhooks to perform name-based conflict checks by fuzzy-matching submitted party names against Clio contacts and matters, logging each check in Google Sheets, emailing a formatted report with Clear/Escalate links, and…