When PagerDuty, Opsgenie, incident.io, Sentry or any other app pages you, Routine Run can start your on-call routine on its own. The first step is on your Lock Screen before you have found your glasses.
This takes about five minutes, once. You build one automation in the Shortcuts app, and Routine Run takes it from there: it picks the routine, ignores repeats of the same alert, and writes down why it did what it did.
The first time you open Routine Run it asks what brought you here. Pick Being on call. That adds When something pages you to your routines and turns on event handling. Nothing else needs changing: any page that reaches Routine Run starts that routine, at any hour.
Already past that screen? Go to Settings › Events from elsewhere and turn on Handling events for other things. Then tap the plus in the middle of the tab bar, Starter routines, and add When something pages you from the Being on call shelf.
The routine's five steps are: Read what actually fired, Say whether it is real, Acknowledge it, Write down what you think is happening, Fix it or hand it on.
Notifications stay quiet under a Focus and with the silent switch on. If your phone lies face down at night, open the first step, Read what actually fired, and under Timing set When it is reached to Wake me. The step then rings as an alarm the moment the run starts, through Focus and the silent switch.
Open the Shortcuts app, go to the Automation tab, and tap +. Choose the Notification trigger and pick your paging app, so it reads "When I get a notification from PagerDuty".
Turn on Run Immediately (on some versions the switch is Notify, and you turn it off). Without this, every page waits for you to tap a banner first, which defeats the point.
Add no filter on the words. Routine Run already decides what to do with each alert.
If your version of Shortcuts puts the trigger at the top of a shortcut instead of in an Automation tab, the same choices apply there: when I receive a notification from your paging app, Automation on, Notify off.
Do not add your paging app to the Routine Run Bridge's trigger. Keep this a separate automation.
Add an action, search for Handle Event, and pick the one from Routine Run. It reads "Handle Title from Source App". Tap each blue field and pick from the Notification variable the trigger hands you:
Leave everything else empty, the Routine field included. A page nothing else is wired to goes to When something pages you.
A notification carries no identifier, so Event ID stays empty and repeats are matched on the app, the title and the message. If your paging app puts an incident number in the text, a source can read it instead — see the last section.
Tap Done.
In Routine Run, go to Settings › Events from elsewhere and tap Send a test event. It goes through the same door as Handle Event, so the answer is what a real page would get. "Matched When something pages you." means the run started, and the line after it says the page went there because nothing else was wired.
That checks Routine Run's half. To check the whole chain, automation included, send a test push from your paging app's own settings.
Lock the phone and look:
The run is named after the incident: its number when the alert has one, such as
#4821, and its title when it does not.
Open History › Decisions first. The reason is written there in plain words:
Keep Ask before running in Settings off. An automation runs with nobody at the phone, so there is nobody to ask.
One automation per paging app, all with the same Handle Event action. To send one app's
pages to a different routine, go to the Data tab, Set
up, Sources, and tap New. Give it a name, set
Matches source containing to the app's name (for example
opsgenie), and pick the Routine. Sources are checked from
the top down and the first match wins. Anything no source matches still goes to When
something pages you.
A source is also where you say where the incident number is. Under Telling two
alerts apart, set Event ID is to an expression that finds it:
#(\d+) for PagerDuty, ([A-Z]+-\d+) for a tool that writes
INC-1234. Repeats are then matched on that number rather than on the
wording, and the run is named after it.
A source can also run its own routine when an event from that app cannot be handled, under When this source cannot be handled.
Shortcuts has no notification trigger there, so nothing starts on a page by itself. Everything else works: Handle Event, the on-call routine, the rules, the journal, the Lock Screen card and the watch. The app says so on the phone itself, under Settings › Events from elsewhere and on the Sources screen.
What you can do instead: