- Automations
- Aderant + Jira
AI-native automation
Automate work across
Aderant and
Jiraby teaching Caddi like a new hire.
Pick any number of tools and Caddi automates them end-to-end. No workflow builder. You teach it the job once, the way you'd train someone new.
Help me automate email-to-Jira in Aderant and Jira. Caddi builds the loop and runs it.


See it on your stack
See Caddi run Aderant and Jira together.
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 · 70+ tools across legal, finance, and operations
One continuous loop.
- 01Measure
Caddi watches how the work gets done today.
- 02Create
You teach it the job once. The loop ships.
- 03Improve
Caddi flags upgrades to existing loops and new automations to deploy.
Practical ways to use Aderant and Jira together
- 01
Create issue in Jira when new time entry in Aderant.
Caddi watches Aderant for new time entry and create issue in Jira — no copy-paste, no missed records.
- 02
Create matter in Aderant when new issue in Jira.
Caddi watches Jira for new issue and create matter in Aderant so the two systems stay in lockstep.
- 03
Update issue in Jira from Aderant events.
When invoice generated happens in Aderant, Caddi update issue in Jira with the right context attached.
Actions Caddi can take across Aderant and Jira
AderantNew time entry
Triggers when a timekeeper posts time against a matter.
AderantInvoice generated
Triggers when an Aderant invoice is finalized.
AderantMatter opened
Triggers when a new matter is opened in Aderant.
AderantCreate matter
Open a new Aderant matter with client, billing, and intake fields.
AderantPost time entry
Record a timekeeper's time against a matter and activity code.
AderantCreate invoice
Generate an invoice for one or more matters.
AderantUpdate client
Push contact, billing, or conflicts data back into the client record.
JiraNew issue
Triggers when a new issue is created.
JiraIssue updated
Triggers when an issue is modified.
JiraIssue transitioned
Triggers when an issue moves to a new status.
JiraCreate issue
Add a new Jira issue with assignee, priority, and labels.
JiraUpdate issue
Modify fields on an existing issue.
JiraAdd comment
Post a comment on an issue.
JiraTransition issue
Move an issue to a different workflow status.
Common questions
How does Caddi connect Aderant and Jira?
Aderant and Jira 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 Jira 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 Jira to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Aderant + Jira 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.
Ready to automate Aderant and Jira?
Drop your work email and we'll show you Caddi running end-to-end against Aderant, Jira, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.




