Chase overdue client documents with Clio and SMTP email escalations
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 20 nodes and runs on a schedule (cron 0 8 * * *). It uses only n8n's built-in nodes.
How it runs
Trigger: On a schedule (cron 0 8 * * *).
- Fetch Firm Users From Clio (HTTP Request): calls an HTTP API (GET)
- Fetch Open Matters From Clio (HTTP Request): calls an HTTP API (GET)
- Fetch Outstanding Document Tasks From Clio (HTTP Request): calls an HTTP API (GET)
- Split Out: splits a list into separate items
- Filter: keeps only the items that match a condition
- Calculate Overdue Days And Tier (Code): runs custom JavaScript code
- Filter: keeps only the items that match a condition
- Check For Reminders Today (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Build Document Reminder Email Body (Code): runs custom JavaScript code
…plus 6 more steps. See the full node list below.
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)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Split Out
n8n-nodes-base.splitOut - Filter
n8n-nodes-base.filter - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - Execute Sub-workflow
n8n-nodes-base.executeWorkflow - Send Email
n8n-nodes-base.emailSend
From the author
Quick Overview This workflow runs daily and uses the Clio API to find overdue “Document Request” tasks, then sends tiered reminder emails to clients via SMTP after passing them through a compliance approval sub-workflow, and escalates urgent items to internal…