The problem
Merak Legal is a California lemon-law firm. Its cases lived in Clio, email and spreadsheets. There was no single screen showing what was overdue, who was carrying how many matters, or whether the three sources agreed with each other. Checking any of that meant opening Clio, then the inbox, then a spreadsheet, and comparing by eye.
What was built
A case-management dashboard sitting on top of Clio.
- Clio pushes changes over webhooks into a local Postgres store. The dashboard reads from that store, so matters, tasks, deadlines and workload load without a Clio API call per page view.
- Clio expires webhook subscriptions, so a scheduled job renews them. Without it the dashboard would quietly stop receiving updates.
- Intake documents go through Gemini for field extraction, replacing manual re-typing. Low-confidence extractions go to review instead of being written.
Write-back is one-way on purpose
Writing changes back to Clio is fully implemented, but it ships behind a feature gate and is currently off. Clio stays the system of record; the dashboard reads from it. Where an edit will not propagate back, the interface says so rather than accepting the edit and dropping it.
Stack
- Application: Next.js, Supabase (Auth, Postgres, Edge Functions)
- Integration: Clio REST API and webhooks, with scheduled subscription renewal
- Orchestration: n8n
- AI: Google Gemini, for document extraction with human review
- Deployment: Docker on Railway
Credentials
Our Apollo.io node is published on npm as
n8n-nodes-apollo (MIT, maintainer arturl95,
14 resources, source public). We hold n8n Verified Creator status.