Microsoft Teams
Create a Teams workflow that receives webhook requests and a HotCodePush webhook in Teams format, so every subscribed event posts to the channel as a card.
HotCodePush posts a card to a Microsoft Teams channel for every event you subscribe to. A Teams workflow gives you the URL, and a HotCodePush webhook in the teams format posts an Adaptive Card to it.
Microsoft retired the Office 365 connectors in May 2026, so a connector URL under webhook.office.com no longer works.
Prerequisites
- You have an organization whose plan includes webhooks. Billing and MAU lists what each plan includes.
- You hold the Admin or Owner role there.
- You have the right to add a workflow to the channel's team.
Create the workflow in Teams
If the channel already has a workflow with the webhook trigger, skip to step 4.
- Open the channel's menu in Teams and choose Workflows.
- Pick the template Send webhook alerts to a channel. A workflow of your own needs the trigger When a Teams webhook request is received and the action Post card in a chat or channel.
- Name the workflow, confirm the team and channel, and save it.
- On the workflow's details page, copy the webhook URL.
- Set the trigger's Who can trigger the flow to Anyone, since HotCodePush sends no authentication token.
The URL is the secret
Anyone who holds the URL can post to the channel. Keep it out of code and chat.
Create the webhook in HotCodePush
- Open your organization in the console, then Settings › Webhooks, and choose Create webhook.
- Enter a name, choose the format Microsoft Teams and paste the workflow's URL.
- Pick the events to deliver. Pick one app as the filter when the channel should follow one app only.
- Choose Create. The webhook is enabled at once.
Events and payload lists every type. Webhooks has the card's format and the delivery log. Signature and retries covers the retries. The card posts under the Workflows bot's name.
Send a test event
In the console, open the webhook and choose Test. From the CLI:
npx hotcodepush webhook test --webhook "Releases to Teams"If the delivery succeeded but no card appeared, read the workflow's run history in the Workflows app. If nothing happens, see the delivery log on Webhooks.
Next steps
- Webhooks explains the card's format and the delivery log. Signature and retries covers the retries.
- Roll out gradually explains the auto-pause rule behind the paused and failure-rate events.
- Slack and Discord show the same setup for the other targets.
Last updated on
Discord
Create a Discord channel webhook and a HotCodePush webhook in Discord format, and every subscribed release event posts to the channel without pinging anyone.
Slack
Create a Slack incoming webhook and a HotCodePush webhook in Slack format, and every release, pause and rollback you subscribe to posts to the channel.