- Automations
- Jira + Zendesk
AI-native automation
Automate work across
Jira and
Zendeskwith Caddi AI Agents.
Automate anything you do across Jira, Zendesk, 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 Zendesk

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

Connect Zendesk to Caddi
Allow2Sign in to Zendesk
The same click again. Both tools are connected.
Create ticket in Zendesk when new issue in Jira.
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 Zendesk together
- 01
Create ticket in Zendesk when new issue in Jira.
Caddi watches Jira for new issue and create ticket in Zendesk. No copy-paste, no missed records.
- 02
Create issue in Jira when new ticket in Zendesk.
Caddi watches Zendesk for new ticket and create issue in Jira so the two systems stay in lockstep.
- 03
Update ticket in Zendesk from Jira events.
When issue updated happens in Jira, Caddi update ticket in Zendesk with the right context attached.
Actions Caddi can take across Jira and Zendesk
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.
ZendeskNew ticket
Triggers when a new ticket is created.
ZendeskTicket status changed
Triggers when a ticket's status changes.
ZendeskNew comment
Triggers when a new comment is added to a ticket.
ZendeskCreate ticket
Open a new Zendesk ticket with subject, priority, and assignee.
ZendeskUpdate ticket
Modify an existing ticket's status, priority, or assignee.
ZendeskAdd comment
Post a public or internal comment on a ticket.
Common questions
How does Caddi connect Jira and Zendesk?
Jira and Zendesk 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 Zendesk 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 Zendesk to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Jira + Zendesk 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 Jira and Zendesk?
Drop your work email and we'll show you Caddi running end-to-end against Jira, Zendesk, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.






