Auto-file emailed documents to Clio matters in Google Drive with compliance logs
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 21 nodes and runs when a new email arrives over IMAP. Along the way it connects Google Drive.
How it runs
Trigger: When a new email arrives over IMAP.
- Extract Metadata From Email (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Fetch Contact By Sender Email (HTTP Request): calls an HTTP API (GET)
- Filter Exact Contact Match (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Fetch Open Matters For Contact (HTTP Request): calls an HTTP API (GET)
- Build Manual Filing Alert (Code): runs custom JavaScript code
- Determine Relevant Matter (Code): runs custom JavaScript code
- Log Unmatched Filing Compliance (Execute Sub-workflow): calls another n8n workflow
- If: checks a condition and branches into true / false
…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 (8)
- Email Trigger (IMAP)
n8n-nodes-base.emailReadImap - 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 - Execute Sub-workflow
n8n-nodes-base.executeWorkflow - Send Email
n8n-nodes-base.emailSend
From the author
Quick Overview This workflow monitors an IMAP intake mailbox, matches inbound email attachments to a Clio contact and open matter, and files the documents into the correct Google Drive matter folder while logging outcomes to a compliance audit sub-workflow…