AI-native automation
Automate work across
Filevine and 
Jirawith Caddi AI Agents.
Automate anything you do across Filevine, Jira, 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 Filevine and Jira
Connect Filevine to Caddi
Allow1Sign in to Filevine
One click with your own Filevine login. No API keys.
Connect Jira to Caddi
Allow2Sign in to Jira
The same click again. Both tools are connected.
Create issue in Jira when new project in Filevine.
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 Filevine and Jira together
In a law firm the work between Filevine and Jira 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
Create issue in Jira when new project in Filevine.
Caddi watches Filevine for new project and create issue in Jira. No copy-paste, no missed records.
- 02
Create project in Filevine when new issue in Jira.
Caddi watches Jira for new issue and create project in Filevine so the two systems stay in lockstep.
- 03
Update issue in Jira from Filevine events.
When phase changed happens in Filevine, Caddi update issue in Jira with the right context attached.
Actions Caddi can take across Filevine and Jira
- Filevine
New project
Triggers when a new project (matter) is created.
- Filevine
Phase changed
Triggers when a project advances to a new phase.
- Filevine
New activity
Triggers when a note, task, or call is added.
- Filevine
Document uploaded
Triggers when a document is added to a project.
- Filevine
Create project
Open a new Filevine project with intake, contacts, and section data.
- Filevine
Create contact
Add a contact to a project with role and relationship data.
- Filevine
Upload document
Add a document to a project with optional metadata.
- Filevine
Create task
Schedule a follow-up task against a project or team member.
- Filevine
Add note
Append a timestamped note to a project's activity feed.
- 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 Filevine and Jira?
Filevine and Jira 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 Filevine and Jira 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 Filevine and Jira to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Filevine + 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 that first walkthrough. The Caddi team reviews every loop before it runs in production.
Does this work for law firms?
Yes. Caddi runs Filevine and Jira 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 Filevine and Jira?
Drop your work email and we'll show you Caddi running end-to-end against Filevine, Jira, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.