Send invoice reminders and partner escalations with Clio and SMTP
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.
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - Send Email
n8n-nodes-base.emailSend - Execute Sub-workflow
n8n-nodes-base.executeWorkflow
What it does
Quick Overview This workflow runs daily to fetch overdue invoices from Clio, assigns each invoice a reminder step based on days past due, and sends either compliance-checked client reminder emails or a 60+ day internal escalation alert to a managing partner via SMTP email. How it works 1. Runs every day at 8am to check for overdue invoices. 2. Fetches up to 200 overdue invoices from the Clio API. 3. Calculates days overdue for each invoice and selects only those that fall into reminder windows (days 1–2, 7–8, 14–15, 30–31, or 60+). 4. Skips processing when no invoices are due for a reminder today. 5. Routes invoices that are 60+ days overdue to an internal partner escalation path and emails the managing partner the invoice details and payment link. 6. Builds a client reminder email for day 1/7/14/30 invoices, runs a separate compliance/opt-out guardrail workflow, and sends the approved message to the client via SMTP. Setup 1. Set up Clio API access and add an HTTP Header Auth credential (Bearer token), then set the CLIOBASEURL variable (for example, https://app.clio.com or https://eu.app.clio.com). 2. Configure an SMTP email credential and set the sender address variable FIRMFROMEMAIL. 3. Create and activate the compliance guardrail workflow, then set GUARDRAILWORKFLOWID so this workflow can call it for opt-out checks and message/footer handling. 4. Add the firm-specific variables used in emails: FIRMNAME, FIRMEMAIL, FIRMPARTNEREMAIL, and (optionally) FIRMPAYLINK as a fallback when Clio share URLs are missing. 5. Adjust the schedule trigger cron expression if you want a different run time or frequency.