AI-native automation
Automate work across
Jira and 
NetDocumentswith Caddi AI Agents.
Automate anything you do across Jira, NetDocuments, 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 NetDocuments
Connect Jira to Caddi
Allow1Sign in to Jira
One click with your own Jira login. No API keys.
Connect NetDocuments to Caddi
Allow2Sign in to NetDocuments
The same click again. Both tools are connected.
Upload document in NetDocuments 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 NetDocuments together
In a law firm the work between Jira and NetDocuments is organized by matter: the right client, the right matter, the right people on it. Caddi carries that context through every step, so nothing is filed against the wrong case.
- 01
Upload document in NetDocuments when new issue in Jira.
Caddi watches Jira for new issue and upload document in NetDocuments. No copy-paste, no missed records.
- 02
Create issue in Jira when new document in NetDocuments.
Caddi watches NetDocuments for new document and create issue in Jira so the two systems stay in lockstep.
- 03
Create workspace in NetDocuments from Jira events.
When issue updated happens in Jira, Caddi create workspace in NetDocuments with the right context attached.
Actions Caddi can take across Jira and NetDocuments
- 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.
- NetDocuments
New document
Triggers when a document is added to a workspace.
- NetDocuments
Document profiled
Triggers when profile attributes are set on a document.
- NetDocuments
Upload document
Add a document to a workspace with profile attributes.
- NetDocuments
Create workspace
Open a new matter workspace under a cabinet.
- NetDocuments
Search documents
Find documents by content or profile attributes.
- NetDocuments
Update document attributes
Set or change profile fields on a document.
Common questions
How does Caddi connect Jira and NetDocuments?
Jira and NetDocuments 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 NetDocuments 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 NetDocuments to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Jira + NetDocuments 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 law firms?
Yes. Caddi runs Jira and NetDocuments with the matter as the unit of work, so documents, time, and communications land against the right client and matter rather than in a general folder. Firms most often start with intake, document filing, or billing prep.
Ready to automate Jira and NetDocuments?
Drop your work email and we'll show you Caddi running end-to-end against Jira, NetDocuments, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.