How to Route Confluence Page Updates to Microsoft Teams and Slack Simultaneously

Confluence Notifications Across Platforms

Confluence has a native Teams integration — available through the Atlassian Marketplace as "Microsoft Teams for Confluence" — that posts page updates, comments, and space activity to a Teams channel. Confluence also integrates with Slack through a similar marketplace app.

Both integrations exist. Both work for single-platform organizations. The problem, familiar to anyone managing cross-platform enterprise environments, is that each integration routes to one destination. The Confluence Teams integration notifies Teams. The Slack integration notifies Slack. There is no native fan-out.

For documentation teams where engineers work in Slack and project managers or leadership work in Teams, this means:

• A runbook update reaches the SRE team in Slack but not the IT leadership in Teams.
• An incident post-mortem publication reaches engineering in Slack but not the CTO in Teams.
• An architecture decision record reaches developers but not the engineering director monitoring Teams.

Confluence Webhooks

Confluence supports outbound webhooks configured at the space level (Space Settings → Integrations → Webhooks). Webhook events include: page created, page updated, page deleted, comment created, blog post published.

Configure the webhook URL to point to SyncRivo. SyncRivo receives the Confluence event payload and routes to Slack, Teams, Webex, Google Chat, or Zoom — or any combination simultaneously.

Setup (15 minutes):

1. In SyncRivo, connect your Slack workspace and Microsoft Teams tenant via OAuth.
2. Create a Webhook source in SyncRivo. Copy the endpoint URL.
3. In Confluence, navigate to the space you want to monitor. Go to Space Settings → Integrations → Webhooks. Add a new webhook. Paste the SyncRivo URL. Select events: page created, page updated, blog post published, comment created.
4. In SyncRivo, configure routing: runbook updates → Slack #sre-team + Teams #ops-leadership simultaneously; blog post published → all subscribed channels; page deleted in runbook space → Slack #sre-leads for review.
5. Repeat for each Confluence space that needs cross-platform notifications.

Routing by Document Type and Audience

Runbook updated: The SRE team that acts on runbooks is in Slack. The IT leadership that needs to know runbooks are current is in Teams. Route to both platforms simultaneously from one Confluence webhook event.

Incident post-mortem published: This is a high-visibility document in engineering organizations. Engineering teams reviewing the post-mortem are in Slack. Executives who track incident frequency and response quality are in Teams. One publication event, two audiences.

Architecture Decision Record (ADR) created: Senior engineers and architects review ADRs in Slack. Engineering managers and CTOs in Teams benefit from visibility into architectural decisions being made. Route new ADR publications to both.

API documentation updated: Internal developers watching in Slack. External partners or customer-success teams tracking API changes may be in Teams or Google Chat. Route documentation updates to the relevant audience on their platform.

Blog post published (Confluence blog): Team updates, retrospectives, and release notes in Confluence blog format reach all subscribed channels simultaneously — engineering in Slack, leadership in Teams, operations in Webex.

Page deleted in critical space: Runbook or incident record deletions should be flagged immediately to team leads. Route page deletion events from critical spaces to Slack for the SRE lead and Teams for the IT director — before the deletion is missed.

The Atlassian stack — Jira for issues, Confluence for documentation, Trello for lightweight project tracking — benefits significantly from a unified routing layer. SyncRivo can receive webhooks from all three simultaneously and route them to the correct platform and channel, eliminating the need to configure separate native integrations per Atlassian tool per messaging platform.

For the full routing matrix and Confluence webhook setup guide, see the Confluence Notifications in Slack & Teams integration guide.