AI-native automation
Connect Clio and Docusign 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 Docusign together
- 01
Send envelope from template in Docusign when new matter in Clio.
Caddi watches Clio for new matter and send envelope from template in Docusign — no copy-paste, no missed records.
- 02
Create matter in Clio when envelope completed in Docusign.
Caddi watches Docusign for envelope completed and create matter in Clio so the two systems stay in lockstep.
- 03
Send envelope from document in Docusign from Clio events.
When new contact happens in Clio, Caddi send envelope from document in Docusign 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 Docusign
- Clio
New matter
Triggers when a new matter is opened in Clio.
- Clio
New contact
Triggers when a new contact is created.
- Clio
Time entry posted
Triggers when a new time entry is recorded.
- Clio
Communication added
Triggers when a call, email, or meeting is logged.
- Clio
Create matter
Open a new Clio matter with client, billing, and intake fields.
- Clio
Create contact
Add a person or company contact to Clio.
- Clio
Create note
Log a timestamped note against a matter.
- Clio
Create time entry
Record time against a matter with rate and activity code.
- Clio
Upload document
Attach a document to a matter with metadata.
- Docusign
Envelope completed
Triggers when all signers complete an envelope.
- Docusign
Envelope sent
Triggers when an envelope is sent for signature.
- Docusign
Recipient signed
Triggers when a single recipient completes signing.
- Docusign
Envelope declined
Triggers when a recipient declines an envelope.
- Docusign
Send envelope from template
Send a pre-built template out for signature with merged fields.
- Docusign
Send envelope from document
Send an arbitrary document out for signature.
- Docusign
Void envelope
Cancel an in-flight envelope with a reason.
- Docusign
Download signed PDF
Pull the executed PDF and certificate from a completed envelope.
- Docusign
Move envelope
Move a completed envelope to a specified folder.
Common questions
How does Caddi connect Clio and Docusign?
Clio and Docusign 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 Docusign 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 Docusign to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Clio + Docusign 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 Docusign?
Drop your work email and we'll show you Caddi running end-to-end against Clio, Docusign, and the rest of your stack.