- Automations
- Box + Jira
AI-native automation
Connect Box and Jira 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 Box and Jira together
- 01
Create issue in Jira when new file in folder in Box.
Caddi watches Box for new file in folder and create issue in Jira — no copy-paste, no missed records.
- 02
Upload file in Box when new issue in Jira.
Caddi watches Jira for new issue and upload file in Box so the two systems stay in lockstep.
- 03
Update issue in Jira from Box events.
When folder shared happens in Box, Caddi update issue in Jira 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 Box and Jira
BoxNew file in folder
Triggers when a file is uploaded to a watched folder.
BoxFolder shared
Triggers when a folder collaboration is added.
BoxUpload file
Add a file to a Box folder with metadata.
BoxCreate folder
Create a new folder under a parent with permissions.
BoxSearch files
Find files or folders with advanced search filters.
BoxMove file
Move a file between folders.
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 Box and Jira?
Box and Jira 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 Box and Jira 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 Box and Jira to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Box + 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 the screenshare. The Caddi team reviews every loop before it runs in production.
Ready to automate Box and Jira?
Drop your work email and we'll show you Caddi running end-to-end against Box, Jira, and the rest of your stack.




