AI-native automation
Automate work across
Aderant and 
Congawith Caddi AI Agents.
Connect Aderant and Conga: Generate document in Conga when new time entry in Aderant. Teach Caddi the job once, the way you'd train someone new, and it runs end to end. No workflow builder.
Discover, automate and govern the work between Aderant and Conga
Caddi AI Agents find the repetitive handoffs between Aderant and Conga, learn them the way a new hire would, and run them for you, with every run on the record. No workflow builder, no code.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
What Caddi is and how it works
An AI teammate that runs your back-office loops.
- Doesn't break. Caddi reads intent, so when fields move or UIs change, your loop keeps running.
- Taught like a new hire. Walk Caddi through the work once. Tweak it later by chat, with no workflow builder to re-architect.
SOC 2 attested · Human-in-the-loop · Full audit trail · 150+ tools across legal, finance, and operations
Practical ways to use Aderant and Conga together
In a law firm the work between Aderant and Conga is organized by matter: the right client, the right matter, the right people on it. Caddi carries that context through every step, so nothing is filed against the wrong case.
- 01
Generate document in Conga when new time entry in Aderant.
Caddi watches Aderant for new time entry and generate document in Conga. No copy-paste, no missed records.
- 02
Create matter in Aderant when document generated in Conga.
Caddi watches Conga for document generated and create matter in Aderant so the two systems stay in lockstep.
- 03
Send for signature in Conga from Aderant events.
When invoice generated happens in Aderant, Caddi send for signature in Conga with the right context attached.
Actions Caddi can take across Aderant and Conga
- Aderant
New time entry
Triggers when a timekeeper posts time against a matter.
- Aderant
Invoice generated
Triggers when an Aderant invoice is finalized.
- Aderant
Matter opened
Triggers when a new matter is opened in Aderant.
- Aderant
Create matter
Open a new Aderant matter with client, billing, and intake fields.
- Aderant
Post time entry
Record a timekeeper's time against a matter and activity code.
- Aderant
Create invoice
Generate an invoice for one or more matters.
- Aderant
Update client
Push contact, billing, or conflicts data back into the client record.
- Conga
Document generated
Triggers when Conga produces a document from a template.
- Conga
Contract executed
Triggers when a contract is fully signed.
- Conga
Approval requested
Triggers when a document is sent for approval.
- Conga
Generate document
Run a Conga template against a CRM record.
- Conga
Send for signature
Route a generated document for e-signature.
- Conga
Update contract
Write status and dates back to the contract record.
Common questions
How does Caddi connect Aderant and Conga?
Aderant and Conga just run together. You teach Caddi the way you'd teach a new hire: walk it through how you use them today, with no workflow builder to wire up. Caddi turns that walkthrough into a verified loop and runs it against Aderant and Conga end-to-end.
Do I need engineering help?
No. Whoever does the work today walks Caddi through it on a call, the same way they'd train a new hire. 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, and once the loop ships it runs as deterministic code, repeatable and logged, with any model step scoped and reviewable.
Can Caddi connect Aderant and Conga to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Aderant + Conga 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 that first walkthrough. The Caddi team reviews every loop before it runs in production.
Does this work for law firms?
Yes. Caddi runs Aderant and Conga with the matter as the unit of work, so documents, time, and communications land against the right client and matter rather than in a general folder. Firms most often start with intake, document filing, or billing prep.
Ready to automate Aderant and Conga?
Drop your work email and we'll show you Caddi running end-to-end against Aderant, Conga, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.