CircleCI's Slack orb is one of the most widely used orbs in the CircleCI ecosystem. In your .circleci/config.yml, you declare the orb, configure a Slack bot token, and use the slack/notify step or the on_fail / on_success hooks to send build status to a Slack channel. It is clean, pipeline-native, and well-documented.
orbs:
slack: circleci/slack@4.12.5
jobs:
build:
steps:
- slack/notify:
event: fail
channel: C0123456789
mentions: '@oncall'
Teams users get nothing from this. The orb authenticates against the Slack API. It has no mechanism to post to Teams, Webex, Google Chat, or Zoom.
What the Teams Gap Looks Like in Practice
A build fails on the main branch at 2:47 AM. The CircleCI Slack orb fires. The on-call engineer sees the Slack alert. The engineering manager — who uses Teams — sees nothing until they check CircleCI directly or get a Slack forward in their morning standup.
For a 5-engineer team all on Slack, this is fine. For an organization where engineers are on Slack and engineering leadership, PMs, or stakeholders are on Teams, the notification gap means Teams users are always one step behind the build status.
The Two Configuration Approaches for Teams
Both approaches need a Teams-side target that accepts an HTTP POST and posts a message into a Teams channel: a Teams Workflows or incoming-webhook flow, or a small relay you host. SyncRivo is not that target — it has no inbound webhook endpoint for CI events and does not route payloads.
Option 1 — CircleCI project webhook (no pipeline changes required):
In CircleCI, go to Project Settings → Webhooks. Add a webhook with your Teams-side URL as the receiver URL. Subscribe to workflow-completed and job-completed events. The Teams-side flow formats the payload and posts it.
No changes to your .circleci/config.yml. The webhook fires at the project level for every pipeline run.
Option 2 — run step with curl (pipeline-controlled):
In your .circleci/config.yml, add a run step that POSTs to your Teams-side URL in an on_fail or on_success context:
- run:
name: Notify Teams on failure
when: on_fail
command: |
curl -X POST $TEAMS_WEBHOOK_URL \
-H "Content-Type: application/json" \
-d '{"event":"build.failed","job":"'"$CIRCLE_JOB"'","branch":"'"$CIRCLE_BRANCH"'"}'
Store the URL as a CircleCI environment variable (TEAMS_WEBHOOK_URL). This approach gives you full control over the payload — include the branch name, commit SHA, job name, and any custom context you want in the notification. Keep the Slack orb in place for the Slack side.
Deciding Which Events Belong Where
- workflow-completed (status: failed) → on-call Slack channel (orb) and engineering leadership Teams channel (Teams-side webhook)
- workflow-completed (status: success, deploy workflow) → release Teams channel and engineering Slack channel
- job-completed (status: failed, test job) → dev Slack channel only
- manual approval required → the approver's platform
Where SyncRivo Fits (and Where It Doesn't)
SyncRivo does not relay messages posted by bots or apps, so a CircleCI orb post in Slack is not copied to Teams by SyncRivo.
What SyncRivo bridges is the human conversation. Connect the on-call Slack channel to the engineering leadership Teams channel, and the 2:47 AM exchange — the engineer's "looking at it", the fix, the decision to hold the release — is visible on both platforms, in both directions, with threads, edits, files, and @mentions kept in sync. The manager reads and replies in Teams; the engineer never leaves Slack.
For the CircleCI webhook setup walkthrough and run-step examples, see the CircleCI Notifications in Slack & Teams integration guide.
Ready to connect your messaging platforms?
