Connect noombat to Microsoft Teams

• Any team member can do this: no Microsoft 365 admin, no app registration, no consent flow. Some organisations restrict who may add apps to a team; if that is you, bring whoever manages the team.
• It is free. The Workflows app ships with Teams on every business plan, and the webhook uses no premium licence and no user seat.
• The alerts channel must be a standard channel. Your team being private is fine; it is private channels (the ones with a lock icon) that Microsoft's posting bot cannot write to.
• GCC, GCC High and DoD tenants: Microsoft provides no posting bot in US Government clouds. Contact us for the alternative setup instead of following this guide.

1. 1Pick or create the channel
2. 2Add the webhook workflow
3. 3One quick check, then send us the link
4. 4If posts fail with "sender is not a member": the fix, step by step

1. 1

   Pick or create the channel about 1 minute

   Alerts read best in a channel of their own. Most customers create one called noombat in the team where the revenue people live. An existing standard channel works too.

   the team > ... > Add channel

   • Name: noombat
   • Channel type: Standard, "Everyone on the team has access"
   • Layout: Posts (alerts are a feed)
   • Tick Recommend that people show this channel in their channel lists, so it does not start out hidden

   

2. 2

   Add the webhook workflow about 2 minutes

   Teams ships a built-in automation template that receives noombat's alerts and posts them as cards. Adding it takes two clicks and creates the link we connect to.

   the channel > ... > Workflows

   

   Type webhook in the search box and pick Send webhook alerts to a channel, the template by Microsoft that uses standard connectors only. Name it noombat and confirm the team and channel.

   

   The workflow's page opens. It is also where its delivery run history lives, which is worth remembering. Click Copy webhook link: that link is what you send us in step 3. It is never shown on screen again, so treat it like a password from here on.

   

3. 3

   One quick check, then send us the link about 2 minutes

   One thing to verify before the link leaves your hands. Microsoft's setup occasionally saves a broken channel selection (the fields show a lone @ instead of your team and channel), and when it does, every post fails while everything looks fine from the outside. Thirty seconds now saves a support round-trip later.

   the workflow's page > Edit

   Look at the Team and Channel fields. If they show your team and channel by name, you are done: click Back without saving. If either shows @ or is empty, re-select your team and channel from the dropdowns, then Save.

   

   Once the link arrives we send a test card the same day and confirm back to you. Then you choose which alerts the channel gets, and they start arriving.

   

4. 4

   If posts fail with "sender is not a member": the fix, step by step about 5 minutes, only when the run history says so

   For that failure the workflow is addressed to a broken target (a lone @ where your team and channel should be), and re-selecting them is the whole fix. The workflow posts from two places internally, and both need it.

   make.powerautomate.com > My flows > the workflow > Edit

   Keep the environment picker, top right, on your Default environment. Expand everything: the flow ends in a fork with a posting action on each side.

   

   Click Post card in a chat or channel 1 (under True). In its Parameters, the Team and Channel fields should name your team and channel. If either shows @ or is empty, open the dropdown and pick them. Leave the Adaptive Card field alone; the pink token in it is correct.

   

   Do the same for Post card in a chat or channel, inside the For each under False. Same two fields, same fix.

   

   Click Save (top right) and wait for the confirmation before closing the tab: an abandoned edit session in this editor is itself a known way to break the workflow. The next alert delivers, and no new link is needed.

Checked against Microsoft Teams's own documentation. Last updated 16 September 2026. Questions, or a policy in the way: integrations@noombat.ai