Confirm when service is restored
When an incident is resolved in Runscope, send an all-clear message through Twilio.
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.
Runscope Explore Runscope →
TriggersFires when a monitor or check in Runscope raises an alert.
Fires when an incident is opened or updated in Runscope.
Fires when a monitored site, service or alarm in Runscope changes state.
Opens a new incident or alert in Runscope.
Acknowledges an open incident in Runscope.
Resolves an incident in Runscope.
Twilio Explore Twilio →
TriggersFires when a new text message is received in Twilio.
Fires when a new call comes in or out through Twilio.
Fires when a call is missed in Twilio.
Fires when a call recording finishes processing in Twilio.
Sends a text message through Twilio.
Starts an outbound call via Twilio.
Creates or updates a contact in Twilio.
Sends a recorded voice message via Twilio.
More Runscope + Twilio workflows
See all Runscope + Twilio integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Confirm when service is restored” between Runscope and Twilio?
Yes — describe it in the box above and Knit's Integrations Agent researches Runscope and Twilio'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 Runscope alerts through Twilio 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 Runscope are sent through Twilio.