AI-native automation
Connect Harvey 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 Harvey and Jira together
- 01
Create issue in Jira when document ready in Harvey.
Caddi watches Harvey for document ready and create issue in Jira — no copy-paste, no missed records.
- 02
Redline document in Harvey when new issue in Jira.
Caddi watches Jira for new issue and redline document in Harvey so the two systems stay in lockstep.
- 03
Update issue in Jira from Harvey events.
When review requested happens in Harvey, 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 Harvey and Jira
- Harvey
Document ready
Triggers when a document is queued for Harvey to process.
- Harvey
Review requested
Triggers when a redline or review is requested on a draft.
- Harvey
Analysis complete
Triggers when Harvey finishes a summary, redline, or extraction.
- Harvey
Redline document
Send a draft to Harvey for AI redlining and markup.
- Harvey
Summarize document
Generate a summary of a document or document set.
- Harvey
Extract clauses
Pull key clauses, terms, or issues from a document.
- Harvey
Answer question
Run a research or document question against Harvey.
- Jira
New issue
Triggers when a new issue is created.
- Jira
Issue updated
Triggers when an issue is modified.
- Jira
Issue transitioned
Triggers when an issue moves to a new status.
- Jira
Create issue
Add a new Jira issue with assignee, priority, and labels.
- Jira
Update issue
Modify fields on an existing issue.
- Jira
Add comment
Post a comment on an issue.
- Jira
Transition issue
Move an issue to a different workflow status.
Common questions
How does Caddi connect Harvey and Jira?
Harvey 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 Harvey 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 Harvey and Jira to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Harvey + 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 Harvey and Jira?
Drop your work email and we'll show you Caddi running end-to-end against Harvey, Jira, and the rest of your stack.