AI-native automation
Automate work across
PagerDuty and 
Twiliowith Caddi AI Agents.
Automate anything you do across PagerDuty, Twilio, 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 PagerDuty and Twilio
Connect PagerDuty to Caddi
Allow1Sign in to PagerDuty
One click with your own PagerDuty login. No API keys.
Connect Twilio to Caddi
Allow2Sign in to Twilio
The same click again. Both tools are connected.
Send SMS in Twilio when incident triggered in PagerDuty.
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 PagerDuty and Twilio together
- 01
Send SMS in Twilio when incident triggered in PagerDuty.
Caddi watches PagerDuty for incident triggered and send sms in Twilio. No copy-paste, no missed records.
- 02
Create incident in PagerDuty when incoming sms in Twilio.
Caddi watches Twilio for incoming sms and create incident in PagerDuty so the two systems stay in lockstep.
- 03
Make call in Twilio from PagerDuty events.
When incident acknowledged happens in PagerDuty, Caddi make call in Twilio with the right context attached.
Actions Caddi can take across PagerDuty and Twilio
- 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.
- Twilio
Incoming SMS
Triggers when a message arrives on a Twilio number.
- Twilio
Call completed
Triggers when a call ends.
- Twilio
Message delivered
Triggers when an outbound message is delivered.
- Twilio
Send SMS
Text a contact from a Twilio number.
- Twilio
Make call
Place an outbound call.
- Twilio
Fetch messages
Pull the message history for a number.
Common questions
How does Caddi connect PagerDuty and Twilio?
PagerDuty 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 PagerDuty 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 PagerDuty and Twilio to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first PagerDuty + 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 PagerDuty and Twilio?
Drop your work email and we'll show you Caddi running end-to-end against PagerDuty, Twilio, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.