- Automations
- Oracle EDM + Twilio
AI-native automation
Automate work across
Oracle EDM and
Twiliowith Caddi AI Agents.
Connect Oracle EDM and Twilio: Send SMS in Twilio when request submitted in Oracle EDM. 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 Oracle EDM and Twilio
Caddi AI Agents find the repetitive handoffs between Oracle EDM and Twilio, 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.
Govern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Govern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Govern 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 Oracle EDM and Twilio together
- 01
Send SMS in Twilio when request submitted in Oracle EDM.
Caddi watches Oracle EDM for request submitted and send sms in Twilio. No copy-paste, no missed records.
- 02
Create request in Oracle EDM when incoming sms in Twilio.
Caddi watches Twilio for incoming sms and create request in Oracle EDM so the two systems stay in lockstep.
- 03
Make call in Twilio from Oracle EDM events.
When request approved happens in Oracle EDM, Caddi make call in Twilio with the right context attached.
Actions Caddi can take across Oracle EDM and Twilio
- 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.
TwilioIncoming SMS
Triggers when a message arrives on a Twilio number.
TwilioCall completed
Triggers when a call ends.
TwilioMessage delivered
Triggers when an outbound message is delivered.
TwilioSend SMS
Text a contact from a Twilio number.
TwilioMake call
Place an outbound call.
TwilioFetch messages
Pull the message history for a number.
Common questions
How does Caddi connect Oracle EDM and Twilio?
Oracle EDM and Twilio 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 Twilio 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 Twilio to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Oracle EDM + Twilio 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 Twilio?
Drop your work email and we'll show you Caddi running end-to-end against Oracle EDM, Twilio, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.






