Time-zone-aware daytime on-call rotation manager for PagerDuty
Try this example in Tines 3B
Import nowThis workflow builds a web UI that generates and syncs follow-the-sun on-call schedules to PagerDuty, ensuring each engineer is on call only during their local business hours (e. g. 9–5) rather than being locked to a single time zone.
The problem
PagerDuty doesn't natively support daytime on-call schedules that follow each engineer's local time zone, forcing global teams to align rotations to a single geography — which means engineers in other regions get paged at inconvenient hours or have to rely on manual workarounds to block alerts. This workflow solves that by letting team leads build and automatically sync follow-the-sun on-call schedules through a simple web UI: it generates one rotation per distinct time zone, anchored so that each engineer is on call only during their own local business hours (e.g., 9–5), while ensuring exactly one person is on call company-wide at any given moment. Changes to the roster — adding people, reordering rotations, or introducing new time zones — sync directly to PagerDuty's shift-based API with no manual schedule editing, and daylight saving transitions handle themselves automatically.
Solution and impact
Teams get a single-page rotation builder that pulls live user profiles from PagerDuty and stores roster configurations locally, then syncs them to real on-call schedules without ever hand-editing shifts in the external tool. By anchoring all rotations to a shared recurrence and creating one rotation per time zone (not per person), the workflow ensures only one engineer is on call at a time across the entire company, respects everyone's local working hours, and adapts to daylight saving changes with no manual intervention. The result is fairer, more sustainable on-call coverage for distributed teams and fewer middle-of-the-night pages for engineers outside the company's primary time zone.
