1. Status Page System
  2. Integrations
Reference

Integrations

Connect monitoring and message delivery to the service record.

  • Status Page System
  • Monitoring source
  • Public destination
  • Subscriber delivery
  • Event source

Systems to connect

  • Monitoring source. Agree which external service signals the team will verify before changing a component or opening an incident.
  • Public destination. Choose the customer-facing status destination that will display the approved component condition and incident message.
  • Subscriber delivery. Connect the channel used for updates intended for Subscribers and check that the audience matches the recorded update.
  • Event source. If a provider is connected, retain its event identifier on each receipt so exceptions can be investigated.

How connections are governed

Admin owns connector access and reviews rejected or failed receipts. Service Owner decides whether a monitored condition represents a visible service change. Communications Reviewer checks the final message and audience. Rehearse an event from source to receipt, incident review and external display. Keep the provider event outcome separate from the incident decision: a receipt marked Applied says the event was handled, while the service owner confirms the actual customer effect.

Set up Status Page System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started