AI-native automation
Automate work across
NetDocuments and 
PagerDutywith Caddi AI Agents.
Automate anything you do across NetDocuments, PagerDuty, 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 NetDocuments and PagerDuty
Connect NetDocuments to Caddi
Allow1Sign in to NetDocuments
One click with your own NetDocuments login. No API keys.
Connect PagerDuty to Caddi
Allow2Sign in to PagerDuty
The same click again. Both tools are connected.
Create incident in PagerDuty when new document in NetDocuments.
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 NetDocuments and PagerDuty together
In a law firm the work between NetDocuments 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 document in NetDocuments.
Caddi watches NetDocuments for new document and create incident in PagerDuty. No copy-paste, no missed records.
- 02
Upload document in NetDocuments when incident triggered in PagerDuty.
Caddi watches PagerDuty for incident triggered and upload document in NetDocuments so the two systems stay in lockstep.
- 03
Add note in PagerDuty from NetDocuments events.
When document profiled happens in NetDocuments, Caddi add note in PagerDuty with the right context attached.
Actions Caddi can take across NetDocuments and PagerDuty
- 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.
- 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 NetDocuments and PagerDuty?
NetDocuments 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 NetDocuments 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 NetDocuments and PagerDuty to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first NetDocuments + 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 NetDocuments 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 NetDocuments and PagerDuty?
Drop your work email and we'll show you Caddi running end-to-end against NetDocuments, PagerDuty, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.