AI-native automation
Automate work across
Filevine and 
PagerDutywith Caddi AI Agents.
Connect Filevine and PagerDuty: Create incident in PagerDuty when new project in Filevine. Teach Caddi the job once, the way you'd train someone new, and it runs end to end. No workflow builder.
Discover, automate and govern the work between Filevine and PagerDuty
Caddi AI Agents find the repetitive handoffs between Filevine and PagerDuty, learn them the way a new hire would, and run them for you, with every run on the record. No workflow builder, no code.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
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 PagerDuty together
In a law firm the work between Filevine and PagerDuty 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 incident in PagerDuty when new project in Filevine.
Caddi watches Filevine for new project and create incident in PagerDuty. No copy-paste, no missed records.
- 02
Create project in Filevine when incident triggered in PagerDuty.
Caddi watches PagerDuty for incident triggered and create project in Filevine so the two systems stay in lockstep.
- 03
Add note in PagerDuty from Filevine events.
When phase changed happens in Filevine, Caddi add note in PagerDuty with the right context attached.
Actions Caddi can take across Filevine and PagerDuty
- 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.
- PagerDuty
Incident triggered
Triggers when a new incident opens.
- PagerDuty
Incident acknowledged
Triggers when a responder acknowledges.
- PagerDuty
Incident resolved
Triggers when an incident is resolved.
- PagerDuty
Create incident
Open an incident on a service.
- PagerDuty
Add note
Post a note to an incident timeline.
- PagerDuty
Resolve incident
Close an incident with a resolution.
Common questions
How does Caddi connect Filevine and PagerDuty?
Filevine and PagerDuty 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 PagerDuty 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 PagerDuty to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Filevine + PagerDuty 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 PagerDuty 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 PagerDuty?
Drop your work email and we'll show you Caddi running end-to-end against Filevine, PagerDuty, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.