Notify customers of an outage
When an incident is opened in PagerDuty, send a status text to affected customers through Telnyx.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
PagerDuty Explore PagerDuty →
TriggersFires when a monitor or check in PagerDuty raises an alert.
Fires when an incident is opened or updated in PagerDuty.
Fires when a monitored site, service or alarm in PagerDuty changes state.
Opens a new incident or alert in PagerDuty.
Acknowledges an open incident in PagerDuty.
Resolves an incident in PagerDuty.
Telnyx Explore Telnyx →
TriggersFires when a new text message is received in Telnyx.
Fires when a new call comes in or out through Telnyx.
Fires when a call is missed in Telnyx.
Fires when a call recording finishes processing in Telnyx.
Sends a text message through Telnyx.
Starts an outbound call via Telnyx.
Creates or updates a contact in Telnyx.
Sends a recorded voice message via Telnyx.
More PagerDuty + Telnyx workflows
See all PagerDuty + Telnyx integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Notify customers of an outage” between PagerDuty and Telnyx?
Yes — describe it in the box above and Knit's Integrations Agent researches PagerDuty and Telnyx's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why send monitoring alerts by SMS?
Chat and email are easy to miss out of hours. Sending critical PagerDuty alerts through Telnyx gets them onto the on-call engineer's phone.
Can I limit texts to serious alerts?
Yes. Filter on severity or monitor name so only the alerts you choose from PagerDuty are sent through Telnyx.