Before you start
- Microsoft Teams with the Workflows app. Microsoft's help page says the webhook templates don't need a premium license.
- Membership of the team and channel the alerts should go to. Private channels work too.
- About five minutes. Chat alerts are on every plan, so there's nothing to upgrade.
Steps
- In Teams, go to the channel for the alerts, select More options (...) next to its name, then Workflows.
- Search for and select the template "Send webhook alerts to a channel". Don't pick the "from specific people" or "from people in an org" versions: those expect a Microsoft sign-in with each request, which a service outside your organization can't send.
- Check the team and channel shown, then select Save.
- On the workflow's details page, copy the webhook link.
- In your dashboard, open Integrations and click Connect on "Slack, Teams or Google Chat". Paste the address into "Incoming-webhook address" and press Save. The page then names the app it recognised, such as "Recognised as Slack".
- Press "Send a test message". A message titled "Test message" with your business name appears in the channel, showing "No action needed" and a link to your leads. If the dashboard says "Not accepted", it also says why.
Platform steps checked on November 13, 2026 against Microsoft Learn: Create an Incoming Webhook (Workflows)
Good to know
- Each new lead, each booking and each request to speak to you is posted: the customer's name, how to reach them, what they need, where and when, the page they asked from, and an "I've got this" link. An urgent lead's title starts with URGENT.
- "I've got this" opens a page with one button. Pressing it marks the lead as handled and stops the email reminders, so two people in the channel don't phone the same customer.
- Alerts appear as a card posted by the Workflows bot. Microsoft doesn't let a webhook set its own name or icon.
- A workflow belongs to the person who made it, not to the channel. If that person leaves your organization, a Teams admin should add a co-owner, or the alerts can stop.
- Teams answers as soon as it has the request and builds the card afterwards. If the test is "accepted" but no card appears, open the Workflows app, find the workflow under Your workflows and check it's turned on.
- Older guides, and webhook addresses on webhook.office.com, are for Office 365 Connectors, which Microsoft switched off in May 2026. Make a new address with Workflows as above.
- Reminders stay in email, so a lead is posted once, not again every time it's chased. Each alert is also sent only once, with no retries. If the app refuses one, the card on Integrations shows Failing and says why, and the email for that lead went out as usual.
- Everyone in the channel sees the customer's phone number and email, so pick a channel only your team is in. Anyone who has the address can post to that channel: treat it like a password. To stop the alerts, clear the field and save.
- Chat alerts aren't tied to a plan. Every account has them, Free and the trial included.
Questions
Are Teams incoming webhooks deprecated?
The old kind is. Microsoft retired Office 365 Connectors, including connector-based incoming webhooks, between May 18 and May 22, 2026. Webhooks made with the Workflows app replace them, and they're what this guide sets up.
Do Teams Workflows need a Power Automate premium license?
Not for this. Microsoft's help page "Create incoming webhooks with Workflows for Microsoft Teams" says the webhook templates and the Teams webhook trigger don't require a premium license.
Can the alerts go to a private channel?
Yes. Microsoft's developer docs say Workflows webhooks support private channels. Every alert carries the customer's phone number, so a private channel is a sensible choice. The lead alerts page shows what else arrives with each lead.