AI-native automation
Automate work across
Oracle EDM and 
PagerDutywith Caddi AI Agents.
Automate anything you do across Oracle EDM, 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 Oracle EDM and PagerDuty
Connect Oracle EDM to Caddi
Allow1Sign in to Oracle EDM
One click with your own Oracle EDM 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 request submitted in Oracle EDM.
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 Oracle EDM and PagerDuty together
- 01
Create incident in PagerDuty when request submitted in Oracle EDM.
Caddi watches Oracle EDM for request submitted and create incident in PagerDuty. No copy-paste, no missed records.
- 02
Create request in Oracle EDM when incident triggered in PagerDuty.
Caddi watches PagerDuty for incident triggered and create request in Oracle EDM so the two systems stay in lockstep.
- 03
Add note in PagerDuty from Oracle EDM events.
When request approved happens in Oracle EDM, Caddi add note in PagerDuty with the right context attached.
Actions Caddi can take across Oracle EDM and PagerDuty
- Oracle EDM
Request submitted
Triggers when a change request is submitted.
- Oracle EDM
Request approved
Triggers when a request is approved and committed.
- Oracle EDM
Node changed
Triggers when a hierarchy node is added or moved.
- Oracle EDM
Create request
Open a change request for accounts or entities.
- Oracle EDM
Fetch hierarchy
Export a hierarchy or node set.
- Oracle EDM
Compare viewpoints
Check two viewpoints for differences.
- 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 Oracle EDM and PagerDuty?
Oracle EDM 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 Oracle EDM 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 Oracle EDM and PagerDuty to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Oracle EDM + 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.
Ready to automate Oracle EDM and PagerDuty?
Drop your work email and we'll show you Caddi running end-to-end against Oracle EDM, PagerDuty, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.