- Automations
- Clio + Doc
AI-native automation
Connect Clio and Doc with AI
Pick any two tools and Caddi runs the loop between them end-to-end — no complicated workflow builder, no IT ticket.
- Doesn't break. Caddi reads intent, so when fields move or UIs change, your loop keeps running.
- Screenshare to set up, chat to improve. Show Caddi once on a screenshare. Tweak it later by chat — no workflow builder to re-architect.
SOC 2 attested · Human-in-the-loop · Full audit trail · 70+ tools across legal, finance, and operations

Practical ways to use Clio and Doc together
- 01
Create document from template in Doc when new matter in Clio.
Caddi watches Clio for new matter and create document from template in Doc — no copy-paste, no missed records.
- 02
Create matter in Clio when new doc shared in Doc.
Caddi watches Doc for new doc shared and create matter in Clio so the two systems stay in lockstep.
- 03
Insert content in Doc from Clio events.
When new contact happens in Clio, Caddi insert content in Doc with the right context attached.
One continuous loop.
- 01Measure
Caddi watches how the work gets done today.
- 02Create
You screenshare it once. The loop ships.
- 03Improve
Caddi flags upgrades to existing loops and new automations to deploy.
Actions Caddi can take across Clio and Doc
ClioNew matter
Triggers when a new matter is opened in Clio.
ClioNew contact
Triggers when a new contact is created.
ClioTime entry posted
Triggers when a new time entry is recorded.
ClioCommunication added
Triggers when a call, email, or meeting is logged.
ClioCreate matter
Open a new Clio matter with client, billing, and intake fields.
ClioCreate contact
Add a person or company contact to Clio.
ClioCreate note
Log a timestamped note against a matter.
ClioCreate time entry
Record time against a matter with rate and activity code.
ClioUpload document
Attach a document to a matter with metadata.
- Doc
New doc shared
Triggers when a new document is shared with you or your team.
- Doc
Doc updated
Triggers when an existing document is edited or commented on.
- Doc
Doc completed
Triggers when a document is marked final or moved out of a draft state.
- Doc
Create document from template
Generate a document from a template with merged fields.
- Doc
Insert content
Append, prepend, or insert text into a document.
- Doc
Replace text
Find-and-replace placeholder values in a document.
- Doc
Convert to PDF
Convert a Word, Doc, or text file into a finalized PDF.
- Doc
Share with collaborators
Grant view, comment, or edit access to a document.
Common questions
How does Caddi connect Clio and Doc?
Clio and Doc just run together. All it takes is showing us how you use them — one screenshare, no workflow builder to wire up. Caddi turns the demo into a verified loop and runs it against Clio and Doc end-to-end.
Do I need engineering help?
No. Whoever does the work today shows it once on a call. Caddi builds the loop. No code, no IT ticket.
Is my data safe?
Yes. Caddi is SOC 2 attested. The AI watches and builds the automation, but once the loop ships it runs deterministically — no model in the loop at runtime.
Can Caddi connect Clio and Doc to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Clio + Doc loop is live, Caddi suggests other tools and other workflows to fold in.
How fast can it go live?
Typical first loops ship within a week of the screenshare. The Caddi team reviews every loop before it runs in production.
Ready to automate Clio and Doc?
Drop your work email and we'll show you Caddi running end-to-end against Clio, Doc, and the rest of your stack.




