Alex Morgan · Principal Engineer
Alex Morgan is a principal engineer at SyncRivo, focused on platform architecture, reliability engineering, and the infrastructure powering real-time messaging interoperability. LinkedIn
April 10, 2026 · 8 min read
Route Statuspage incident created, updated, resolved, and component status change events to Slack, Teams, Webex, Google Chat, and Zoom simultaneously.
Statuspage has no native Microsoft Teams integration. Incident updates reach Slack subscribers — Teams-side stakeholders, leadership, and customer success teams find out when someone manually posts an update or checks the status page directly.
Every Statuspage event — incident lifecycle, component status changes, and maintenance windows — delivered simultaneously to Slack, Teams, Webex, Google Chat, and Zoom.
New incident creation events routed to the on-call Slack channel for immediate response and the engineering leadership Teams channel for executive awareness — simultaneously, as soon as the incident is posted on Statuspage.
Incident update posts — status changes, investigation findings, workaround announcements — routed to the operations Slack channel and the stakeholder Teams channel to keep both audiences informed in real time throughout the incident lifecycle.
Incident resolved and closed events routed to the on-call Slack channel and the leadership Teams channel simultaneously — confirming the incident is closed and service is restored across both platforms without manual status posts.
Component status changes — degraded performance, partial outage, major outage — routed to the operations Slack channel and the customer success Teams channel simultaneously for real-time component-level awareness.
Scheduled maintenance window announcements routed to the customer success Teams channel for advance notice and the engineering operations Slack channel for technical preparation — before the window begins.
Scheduled maintenance completion events routed to the same stakeholder channels as the maintenance announcement — confirming the maintenance window closed and services are fully operational across both platforms.
In Statuspage, go to your page settings → Subscribe to Updates → Manage Subscribers → Add Subscriber → Webhook. Set the subscriber URL to your SyncRivo inbound endpoint. Statuspage sends incident lifecycle events — created, updated, resolved — and component status changes to SyncRivo as HTTP POST requests.
Add Slack channels (on-call, operations, engineering) and Teams channels (Engineering Leads, Customer Success, Executive Communications) as delivery destinations in SyncRivo. Each destination can be targeted by different routing rules for different event types.
Configure per-event routing: incident.create → Slack #on-call + Teams Engineering Leads simultaneously; component major_outage → Slack #operations + Teams Customer Success + Teams Executive; incident.resolve → same channels as incident was opened (closing the notification loop); maintenance.scheduled → Teams Customer Success (advance notice) + Slack #operations.
Point both your PagerDuty webhook and your Statuspage webhook at separate SyncRivo endpoints (or the same endpoint with different routing rules). Route PagerDuty high-urgency alerts to the on-call Slack channel for immediate response. Route Statuspage incident lifecycle events to the broader stakeholder Teams channels as the incident progresses. The response team gets PagerDuty alerts in Slack; leadership gets formal Statuspage incident updates in Teams — automatically, from the same incident.
Route Statuspage events to the right audience — on-call in Slack, customer success and leadership in Teams — based on event type and component severity.
| Statuspage Event | Slack Destination | Teams Destination | Rationale |
|---|---|---|---|
| Incident created (major outage) | #on-call (immediate response) | Engineering Leads + Executive channel | Response team activates; leadership informed simultaneously |
| Incident updated | #operations (update log) | Engineering Leads + Customer Success | Ops tracks investigation; stakeholders see progress in Teams |
| Incident resolved | #on-call + #operations | Engineering Leads + Customer Success | Closes notification loop on all channels simultaneously |
| Component: major_outage | #operations (technical response) | Customer Success channel | Ops investigates; CS notified for customer communications |
| Component: degraded_performance | #operations (monitoring) | — (Slack only unless SLA-critical) | Degraded but not down; Teams notified only if SLA-impacting |
| Maintenance scheduled | #operations (prep notice) | Customer Success channel | Engineers prepare; CS notifies customers in advance |
| Capability | Statuspage Native | SyncRivo |
|---|---|---|
| Notify Slack (via subscriber webhook) | ✓ Webhook subscriber can target Slack incoming webhook URL | ✓ Via SyncRivo endpoint relay |
| Notify Microsoft Teams | ✗ No native Teams integration or Teams webhook destination | ✓ Full Teams channel delivery via SyncRivo routing |
| Notify Webex / Google Chat / Zoom | ✗ Not available natively | ✓ All 5 platforms |
| Single incident event → Slack AND Teams simultaneously | ✗ Webhook subscriber is single-destination | ✓ One SyncRivo endpoint, fan-out to all platforms |
| Route by component (production component → Teams, staging → Slack only) | ✗ One webhook URL per subscriber | ✓ Per-component and per-severity routing rules |
| Route resolved events to same channels as incident opened | ✗ No conditional routing by event type | ✓ Per-event-type routing rules close the notification loop |
| PagerDuty + Statuspage combined incident workflow | ✗ Separate webhook configurations, no unified routing | ✓ Both tools point to SyncRivo; unified routing across both |
| Audit trail for incident communication delivery | ✗ Not provided | ✓ Full event log per delivery |
Atlassian Statuspage does not have a native Microsoft Teams integration for incident notifications. Statuspage supports outbound webhooks for page subscribers — when an incident is created, updated, or resolved, Statuspage fires a webhook to configured subscriber URLs. There is no built-in Teams connector or Teams webhook destination in Statuspage. For organizations where IT operations uses Slack but engineering leadership, executive stakeholders, or customer success teams use Teams, configure a Statuspage subscriber webhook pointing to SyncRivo. SyncRivo routes incident events to Slack, Teams, Webex, Google Chat, and Zoom simultaneously.
In Statuspage, go to your page settings → Subscribe → Webhook. Add a new webhook subscriber with your SyncRivo inbound endpoint as the URL. Statuspage will POST incident lifecycle events — incident created, incident updated, incident resolved, component status changed — to SyncRivo. SyncRivo routes the payload to your configured Teams channel in real time. Configure destination channels in SyncRivo to target the correct Teams channels for your stakeholder audience.
SyncRivo routes any Statuspage webhook event: incident.create (new incident opened), incident.update (incident update posted), incident.resolve (incident resolved and closed), component.update (component status changed — degraded_performance, partial_outage, major_outage, operational), maintenance.scheduled (scheduled maintenance created), maintenance.start (scheduled maintenance began), maintenance.complete (scheduled maintenance completed). Configure routing rules in SyncRivo — route major outage events to both the on-call Slack channel and the engineering leadership Teams channel simultaneously; route resolved events to the same channels for incident closure confirmation.
Yes. Statuspage component status changes (component.update events) are included in Statuspage webhook payloads. When a component transitions to degraded_performance, partial_outage, or major_outage, SyncRivo receives the webhook and routes to Teams, Slack, Webex, Google Chat, and Zoom based on your routing configuration. Route component degradation events for production-critical components to both the operations Slack channel and the customer success Teams channel simultaneously — so customer-facing teams have real-time awareness without waiting for a manual status communication.
A common incident management architecture uses PagerDuty for on-call alerting and Statuspage for external and internal status communication. PagerDuty can update Statuspage automatically via the PagerDuty-Statuspage integration. With SyncRivo, configure both PagerDuty and Statuspage webhooks pointing to SyncRivo inbound endpoints. Route PagerDuty high-urgency alerts to the on-call Slack channel immediately; route Statuspage incident lifecycle events to the broader stakeholder Teams channels as the incident progresses. This gives the response team real-time PagerDuty alerts in Slack and formal incident communications to leadership in Teams — from the same incident, automatically.
Yes. Statuspage scheduled maintenance events (maintenance.scheduled, maintenance.start, maintenance.complete) are included in Statuspage webhook payloads. Configure SyncRivo routing rules to route scheduled maintenance notifications to the customer success Teams channel for advance notice, the operations Slack channel for technical awareness, and the engineering leadership Teams channel for visibility — all from a single Statuspage webhook pointing to SyncRivo. Route maintenance.complete events to the same channels to confirm the maintenance window closed successfully.
Statuspage keeps subscribers informed. SyncRivo ensures your Teams-side stakeholders — leadership, customer success, compliance — receive incident updates simultaneously with your Slack team, automatically.
Ready to connect? Slack ↔ Teams connection setup →