Skip to main content
Version: Next

On-Call Roster

Looks up the roster and attaches the people currently on shift to the message, ready for a send node to use.

Type: user-roster · Category: Notification · Ports: one input · one output

The On-Call Roster node as it appears on the pipeline canvas.The On-Call Roster node as it appears on the pipeline canvas.

When to use it​

  • Any notification that should reach whoever is on duty rather than a fixed list
  • Escalation paths that differ by shift or by day of the week

Settings​

SettingKeyPurpose
User databasedbIdWhich user database holds the roster.
RosterrosterIdWhich roster to resolve.

Example — notifying whoever is actually on shift​

Alarm (raised, critical) → On-Call Roster → Send Email

Out — the alarm payload, with the resolved recipients attached:

{
  "payload": {
    "name": "Motor1 overspeed",
    "priority": "critical",
    "recipients": [
      { "name": "A. Fitter", "email": "a.fitter@example.com", "phone": "+62811…" }
    ]
  }
}

Why it matters​

This is the node that stops notification lists going stale. Hard-coding addresses in a send node means every shift change is a pipeline edit — and the edit that does not happen is the reason an alarm at 02:00 went to someone on annual leave.

See also​