- Automations
- Jira + Lacerte
AI-native automation
Automate work across
Jira and
Lacertewith Caddi AI Agents.
Automate anything you do across Jira, Lacerte, and the rest of your tools. Sign in, show or tell Caddi what you want, and it runs end to end. No workflow builder.
How to connect Jira and Lacerte

Connect Jira to Caddi
Allow1Sign in to Jira
One click with your own Jira login. No API keys.

Connect Lacerte to Caddi
Allow2Sign in to Lacerte
The same click again. Both tools are connected.
When something new comes in to Jira, update Lacerte.
ScreenshareType it3Show or tell it
Screenshare the job, or type it in chat. Change it any time.
- Running


14 done1 for review
4Watch it run
Caddi does the work and flags anything unsure for review.
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 Jira and Lacerte together
At an RIA the work between Jira and Lacerte is organized by household: the right client, the right accounts, the right advisor. Caddi carries that context through every step, so records stay tied to the household they belong to.
- 01
Keep Jira and Lacerte in lockstep.
Caddi listens for changes on either side and writes the matching update to the other, so your team stops keeping two systems in sync by hand.
Actions Caddi can take across Jira and Lacerte
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 Jira and Lacerte?
Jira and Lacerte 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 Jira and Lacerte 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 Jira and Lacerte to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Jira + Lacerte 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 RIAs and financial advisors?
Yes. Caddi runs Jira and Lacerte with the household as the unit of work, so plans, accounts, and activity stay tied to the right client and advisor. Firms most often start with onboarding, account maintenance, or reporting prep.
Ready to automate Jira and Lacerte?
Drop your work email and we'll show you Caddi running end-to-end against Jira, Lacerte, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.






