Public demo · Automatically signed in · Changes reset every 20 minutes · External checks and messages are disabled. Do not enter private data.
Northwind Hosting

Send out

Tell your team when an incident starts, changes or is resolved

Add a destination

Takes about a minute

  1. Where should updates go?

    Pick the tool your team already watches.

  2. Connect it

    Use the Production URL of a POST webhook. In n8n that is the Webhook node, not HTTP Request.

    Use the production URL of a receiver that accepts JSON over POST. In n8n, choose the Webhook node, not the HTTP Request node.

    Step by step: Generic JSON

    Start an automation when an incident is created or updated.

    1. Create a POST webhook in n8n or your own receiver.
    2. For n8n, publish or activate the workflow and copy its Production URL. A Test URL only works while listening.
    3. Add this destination, then use Send test and check the workflow execution.

    What arrives: JSON contains event and incident. In n8n, read body.event and body.incident. Resolutions arrive as incident.updated with a populated resolved_at.

    Open the setup documentation ↗

  3. Which moments?

    Internal incidents are included too: this goes to your own team, not to subscribers.

  4. Save and test

    A test sends one real message, so you see exactly what your team will see.
    How delivery works

    Messages go out within a minute, from the scheduler. If your tool is down, Pharos retries up to six times with growing pauses; every attempt is in the delivery log. Send test makes one immediate attempt.

    Generic JSON: payload and signature

    Every Generic JSON request carries X-Pharos-Signature, an HMAC SHA256 of the raw body with this page's signing secret. Check it before acting on an event. Slack, Teams and the chat apps are not signed: their URL is the credential.

    {"event": "incident.updated", "incident": {"id": 42, "name": "Mail delayed", "status": "Watching", "impact": "minor", "resolved_at": null, "components": ["Outbound queue"]}}

    Maintenance arrives as maintenance.scheduled, maintenance.started, maintenance.completed or maintenance.cancelled with a maintenance object.

Your destinations

3 on this page
  • Slack #ops alerts Slack · last attempt 22 Oct 20:40 https://hooks.slack.example.net/service… Working
    Sends: Incident opened, Update posted, Resolved
    Change moments
  • Teams support channel Microsoft Teams · last attempt 22 Oct 20:40 https://teams.example.net/webhook… Failing
    Teams support channel answers 503. The receiving side had an error; Pharos retries with growing pauses. See the log
    Sends: Incident opened, Update posted, Resolved
    Change moments
  • n8n workflow Generic JSON · never tried https://n8n.example.net/webhook… Paused
    Sends: Incident opened, Update posted, Resolved
    Change moments

Looking for subscriber emails?

Emails to subscribers are set up under Subscribers and Page email. This screen is for your own team.

Are you sure?