Recued
Menu
← Back to recipes

PagerDuty on-call handoff digest

by recued-core v2 9 views

Use “PagerDuty on-call handoff digest” in Recued. It provides a scheduled, read-only handoff digest for PagerDuty.

How it works 17 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (17 steps)
current_user ?
oncalls_raw ?
schedules_raw ?
incidents_raw ?
defaults defaults
Apply defaults
oncall_count count
Count items in oncalls
schedule_count count
Count items in schedules
incident_count count
Count items in incidents
has_incidents compare
Check if incident count is greater than 0
notify_enabled compare
Check if setting notify when incidents equals true
should_notify all
Check if all conditions are true
notify ?
skip: step.should_notify not_equal true
incident_rows slice
Take a subset of
oncall_rows slice
Take a subset of
incident_table to_table
Format results as a data table
oncall_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 12 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

since setting =
until setting =
channels setting = in_app
end hour setting = 10
weekdays setting = 1,2,3,4,5
pagerduty setting =
row limit setting = 20
start hour setting = 8
schedule ids setting =
incident statuses setting = triggered,acknowledged
escalation policy ids setting =
notify when incidents setting = true

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Send notificationsRead your Pagerduty connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

pagerduty pagerdutyincidentson-callhandoffschedulenotificationpack:pagerduty

Details

17 steps 12 configurable settings recipe_id: on-call-handoff-digest-pagerduty