Outage alerts routed to the on-call person who's actually online

An outage signal becomes an incident task plus a direct message to the on-call person who's currently online. Non-critical events are filtered out.

  • Messages a person, not a channel — someone owns it
  • Checks which on-call member is actually available
  • The incident task is created automatically
  • Minor events don't wake the team
WebhookSlack
Set it upScriptera

How it works

To get sourceCraft notifications in Webhook, you don't need a developer: a ready-made scenario watches events and sends messages for you.

  1. Starts when: Receive Uptime Alert
  2. Check: Filter for Critical Status
  3. If yes: Create New Jira Incident
  4. Then: Get On-Call Channel Members
  5. Check: Split/Process Each Member
  6. Then: Select Active On-Call User
  7. Then: Notify Selected User
  8. Then: Check Slack User Presence
  9. Then: Collect & Set Final Data

You can launch this sourceCraft + Webhook integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios