Microsoft Teams setup

Before you start

• An account with Microsoft Teams

Set it up

1. Create the destination in Teams — with Workflows, not a connector. Open the channel’s menu, choose Workflows, and pick the template “Post to a channel when a webhook request is received”. Creating the flow gives you a URL. Most guides online still tell you to add an Incoming Webhook connector instead: Microsoft retired Office 365 connectors in May 2026, and the outlook.office.com URLs they hand out deliver nothing. Treat the URL you get as a credential — anyone holding it can post to the channel.
2. Add it in SendBeam. Settings → Webhooks → Add endpoint. Choose Microsoft Teams, paste the URL, and tick the events worth interrupting someone for.
3. Send a test event. The button beside the endpoint posts a message marked as a test, so you can confirm it arrives before anything real depends on it.

Code

Directly: SendBeam → a Teams channel

Settings → Webhooks

1. In Teams: the channel → Workflows
     Choose "Post to a channel when a webhook request is received"
     Copy the URL it gives you when the flow is created

2. In SendBeam: Settings → Webhooks → Add endpoint
     Where          A Microsoft Teams channel
     Endpoint URL   the URL the Workflow gave you
     Events         Sending paused, Sending resumed,
                    Delivery results deteriorating,
                    Automation failed, Campaign sent,
                    Domain verified, Domain failed

3. Send test event  — a card appears in the channel, marked as a test

If a guide offers you an Incoming Webhook connector and an outlook.office.com URL, it is out of date: Microsoft retired Office 365 connectors in May 2026 and those URLs deliver nothing. Workflows is the replacement.

In n8n: SendBeam events to a Teams channel

n8n workflow

1. SendBeam Trigger
     Events   Contact Created, Contact Unsubscribed, Form Submitted
2. Microsoft Teams → Message → Send
     Channel  the channel to post in
     Text     {{ $json.event }}: {{ $json.data.contact.email }}

Publishing the workflow sets up the SendBeam webhook for you. Form submissions carry the address as data.email rather than data.contact.email.

In Power Automate: SendBeam webhook to Teams

Power Automate flow

Trigger  When a Teams webhook request is received   (copy its URL)
In SendBeam: Settings → Webhooks → Add endpoint
             Where: Your server — paste the URL, choose contact.created
Action   Post message in a chat or channel
         Message: New subscriber: @{triggerBody()?['data']?['contact']?['email']}

Choose “Your server” rather than “A Microsoft Teams channel” for this route: the flow wants SendBeam’s JSON so it can read the fields, not a finished card.

In Make: SendBeam webhook to Teams

Make scenario

Module 1: Webhooks → Custom webhook   (copy its address)
In SendBeam: Settings → Webhooks → Add endpoint
             Where: Your server — paste the address, choose contact.created
Module 2: the Microsoft Teams module that sends a channel message
          Text: New subscriber: {{1.data.contact.email}}

Run the scenario once and use Send test event on the endpoint in SendBeam, so Make learns the payload’s fields.

In Zapier: SendBeam webhook to Teams

Zap

Trigger  Webhooks by Zapier, catching a hook   (copy its URL)
In SendBeam: Settings → Webhooks → Add endpoint
             paste the URL, choose contact.created
Action   Microsoft Teams's action for sending a channel message
         Text: New subscriber: map Data Contact Email

Webhooks by Zapier is available on Zapier’s paid plans. Send test event in SendBeam gives Zapier a sample with the same fields a real event has.

Things to know

• A Teams channel carries the operational events only — pauses, resumes, deliverability warnings, automation failures, campaign sends and domain results. For contact-level events use one of the automation routes below.
• Each message names its workspace, so several workspaces can point at one channel.
• Messages are sent as Adaptive Cards. Workflows accepts the older MessageCard format too, but does not render buttons on one, so the link to the page that answers the alert would be lost.
• Test events carry test: true in data, and a direct Teams test card says so on its face.
• Microsoft answers “accepted” as soon as it receives a card and runs the Workflow afterwards, so a successful test means it was queued rather than posted — glance at the channel to confirm.
• Set the Workflow trigger to “Anyone”, and add a co-owner: a Workflow is owned by one person, and Microsoft turns it off if that owner leaves.
• The full list of events is in the webhooks documentation.

← Back to the Microsoft Teams integration