outgoing webhook the app doesn't appear when mention

Question

outgoing webhook the app doesn't appear when mention

Anonymous

Hi Team support now I'm trying to connect teams with N8N framwork already create a flow.
the flow is sending message from the teams then send it to n8n then send the reponse to the same channel.
now i can send message from the agent ai in n8n to the channel but i can't send message from teams to the agent ai (n8n component) although I checked the teams docs and i have to create outgoing webhook already created and when trying to mention the name of my created outgong webhook nothing appears tried to clear cache and login adain but nothing change and tried teams web and still the same issue also i want to mention that the app has the premissions to create a get message and send to channels.

0 comments

1 answer

Your answer

Answer 1

Anonymous

Hi @Ahmed Abdelbadea

Welcome to Q&A Community,

As you described, I understand how confusing it can be when the setup looks correct, but the feature just doesn’t behave as expected. Let’s walk through some effective steps to fix this:

Outgoing webhooks only work in public channels (not private or personal chats). Confirm the channel you're testing in is public.

The webhook is added at the team level, but @mentions work in any public channel within that team. If it's a private channel, recreate the webhook in a public one.

Check if the Webhook is listed and remove/re-add it:

Go to the team in Teams > Manage team > Apps tab. Look for "Outgoing webhook" under uploaded apps or connectors. If it's not there or shows as inactive, that's the problem.
Alternatively, in the channel > ... (more options) > Connectors > Search for "Outgoing Webhook" and see if it's configured.
If it's listed but not working, remove it and recreate:
Name: Choose a simple name without spaces or special characters (e.g., "n8nAI").
Callback URL: Your n8n webhook URL (must be HTTPS and publicly accessible; use ngrok or a tunnel if testing locally).
Description and profile picture: Optional, but add them.
When creating, Teams will display an HMAC security token (a secret key)—copy this immediately, as you'll need it for validation in n8n (more on this below).

After recreating, wait 5-10 minutes for propagation, then restart Teams or switch to the web version to test.

Test @Mention Manually (Bypass Autocomplete):
- Autocomplete can lag or fail due to caching/network issues, but you can still type the full @mention manually.
- In the channel, type @YourWebhookName your test message (replace with exact name) and send it. If it resolves (the name turns bold or links), it should trigger the POST to n8n.
- If it doesn't resolve or send, the webhook isn't activated—proceed to validation below.
Implement HMAC Validation in Your n8n Flow: This is likely the root cause: Teams requires HMAC authentication to validate requests. During webhook creation and for every message, Teams sends a POST with an Authorization header containing HMAC <base64-encoded-hmac>. Your n8n flow must verify this against the secret (from creation) to confirm it's from Teams. If validation fails during initial creation, the webhook won't activate fully, leading to no @mention.
In n8n:

-Use a Webhook node as the trigger (this receives the Teams POST).

This setup avoids webhook validation issues and leverages your existing app permissions. If you run into 403 errors when sending, double-check the license and permissions—ensure the user/account has an active Office 365/Teams license.

If none of this resolves it or you share more details (e.g., screenshots of the webhook creation, n8n flow, or exact error in n8n logs), I can dig deeper. Let me know how it goes!

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Anonymous

2025-07-30T07:59:47.9433333+00:00

Hi @Anonymous , thank you for your answer.
If I want to make this flow for a specific channel, just for n of people, how to do that.
Anonymous

2025-07-30T08:17:36.5733333+00:00
Hi @Ahmed Abdelbadea,

Welcome to the Q&A Community

I’m here to assist your problem.

Based on the description you have shared, i can answer for your question:

To restrict your n8n-Teams integration flow to a specific channel and make it accessible only to a limited number of people (e.g., "n" members), the key is to leverage Teams' permission model. Outgoing webhooks are scoped to the entire team (not individual channels), meaning once added, they can be @mentioned in any channel within that team. However, by using a private channel with restricted membership, you can effectively limit who can trigger the flow via @mentions, as only channel members can post messages there. This keeps the bidirectional messaging (Teams to n8n and back) isolated to those n people without affecting the broader team.

Here's how to set it up step by step. This assumes you're a team owner or have the necessary permissions; if not, coordinate with your Teams admin.

1.Create a Private channel in Teams:

Private channels allow you to control exactly who has access, limiting it to your "n" people.

In Microsoft Teams, go to the team where you want to host the integration (or create a new team if needed: Teams tab > Join or create a team > Create team).

In the team, click ••• (More options) next to the team name > Add channel.

Enter a channel name (e.g., "n8n-Flow-Channel").

Under Privacy, select Private – Accessible only to a specific group of people.

Click Create.

Add members: Search for and select exactly the "n" people you want (including yourself for testing). You can add/remove members later via ••• > Manage channel > Members.

Note: Private channels don't appear for non-members, and only members can view/post in them. This ensures only your selected group can @mention the webhook to trigger the n8n flow.

2.Add or verify the outgoing Webhook in the Parent Team:

Since webhooks are team-level, add it to the team containing your private channel.

If you haven't created the webhook yet (or need to recreate for the new team):

In Teams, go to the team > ••• > Manage team > Apps tab.

Click Create an outgoing webhook.

Fill in:

-Name: e.g., "n8nWebhook" (case-sensitive for @mentions).

-Callback URL: Your n8n webhook URL (ensure it's HTTPS and publicly accessible).

-Description: Something like "Triggers n8n AI flow".

Click Create and copy the HMAC token for n8n authentication (as covered in previous steps).

If the webhook already exists in another team, you can recreate it here—webhooks aren't transferable, but your n8n flow remains the same.

3.Test the flow in the Private channel:

Switch to your new private channel.

Type @YourWebhookName test message and send it. This should trigger the POST to n8n.

In n8n:

Ensure your workflow handles the incoming request (with HMAC validation).

Parse the payload to extract the channel/conversation ID (e.g., from channelId or conversation.id in the JSON).

When responding, use the Microsoft Teams node in n8n to send the reply back to the exact channelId and conversationId from the incoming payload. This keeps replies within the private channel.

Noted: Non-members can't access the channel, so they can't trigger or see the flow. If someone outside tries to @mention in a public channel of the same team, it would still work (since the webhook is team-scope)—but to prevent this entirely, instruct users not to use it elsewhere, or consider the bot alternative below for stricter controls.

4.Handle permissions and security:

Ensure the Teams app permissions (for message read/send) are granted at the team level via the Microsoft Graph API or Azure AD if using advanced setups.

In n8n, you can add logic to filter incoming requests: Check the channelId in the payload against your private channel's ID (find it via Teams API or by inspecting a test payload). If it doesn't match, ignore or reject the request.

For added security: If your "n" people change, update channel membership dynamically. Avoid sharing the HMAC token outside n8n.

If the webhook approach feels too open (e.g., usable in other channels of the team), switch to a full bot app, which can be installed/scoped more granularly:

Create a bot in Azure Bot Service (free tier available): Register a bot, get the app ID and password.

In n8n: Use the bot's endpoint as the callback.

Create a Teams app manifest (JSON file) specifying scopes like team and channel.message.send.

Sideload the app: In Teams > Apps > Manage your apps > Upload a custom app > Select your manifest.zip > Install only for your team or specific channel.

Add the bot to your private channel: @mention it there to interact.

This way, the bot is only discoverable/invokable in the installed scope, limiting it strictly to your n people in that channel.

Resources: Check Microsoft's docs for "Create a bot for Teams" and "Outgoing webhooks vs. bots" for comparisons.

This setup keeps everything contained without needing code changes in n8n beyond payload filtering. If you run into issues (e.g., permissions errors), share details like your Teams version or n8n flow errors for more targeted help!

Thank you for your patience and support.

As a forum moderator with a limited scope of knowledge, I hope you find my answer helpful. Please know that I've done my best to assist you.

Thank you for your kindness and understanding. If you need anything else, please feel free to contact me.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment"

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Anonymous

2025-07-31T06:49:59.6866667+00:00

Hi @Ahmed Abdelbadea ,

Welcome to the Q&A Community

I’m here to assist your problem.

Any update on your issue ? Can you tell me about that ?

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment"

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Anonymous

2025-08-04T07:01:08.72+00:00

Hi @Ahmed Abdelbadea ,

Welcome to the Q&A Community

I’m here to assist your problem.

I hope this message reached you.

This is my second time reaching out to check if your issue has been resolved. I really want to make sure your experience is as smooth as possible. If your issue persists or if you encounter any new difficulties, please share more details about the current steps you are taking. I am always happy to assist you whenever you need.

While waiting for your response, I will also be monitoring other customer questions on the forum to assist them. If you have any further questions or updates, please tag (@Sting) in the reply so I can assist you more promptly and thoroughly.

I look forward to hearing from you soon.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment"

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.