Feedback source
Turn Microsoft Teams messages into ranked product insight
Internal feedback usually arrives in Teams, from the people closest to your customers. Mention the webhook and it becomes a triaged item, grouped with everything else.
Why connect Microsoft Teams
- Capture what your own team hears. Sales, support, and success relay customer problems in Teams every day. Those messages stop evaporating.
- No app to publish. An outgoing webhook is a channel setting, not a Teams app that needs tenant approval.
- Triaged with everything else. Teams feedback is deduped and ranked next to your widget, helpdesk, and email items.
"Export keeps timing out on large projects, this is blocking our team."
Deduped and ranked alongside every other source.
How it works
- 1
Create an outgoing webhook
In the channel menu, Connectors, then Outgoing Webhook.
- 2
Paste the callback URL
Copy it from the Teams card in FeedbackFlow.
- 3
Mention it to send
Mentioning the webhook in a message forwards that message for triage.
Prefer the full walkthrough? Read the Microsoft Teams setup guide.
Before you start
- A Teams channel where you can create an outgoing webhook. This is a team-level setting, so you need to be an owner of the team or ask one.
- A FeedbackFlow project. The free plan covers one, and no credit card is needed to finish this setup.
- Agreement on how the team will use it. Because sending requires an @mention, this only works if people know to do it.
How to connect Microsoft Teams to FeedbackFlow
- 1
Create the outgoing webhook
In Teams, open the channel, click the three dots next to the team name, choose Connectors, then Outgoing Webhook, and create one. Give it a name people will recognise when they mention it, because that name is what they will type.
- 2
Set the callback URL
Paste the request URL from the Teams card in your FeedbackFlow project settings. It is unique to your project. Teams will not send anything until this is set.
- 3
Copy the security token into FeedbackFlow
Teams generates a security token when you create the webhook and shows it once. Paste it into the Teams card. FeedbackFlow verifies every delivery against it using HMAC-SHA256 over the raw request body, which is Teams' own scheme, so an unsigned or wrongly signed request is rejected outright.
- 4
Mention the webhook in a message
Type @ followed by the webhook's name, then the feedback. The message arrives in FeedbackFlow within seconds. The @mention itself is stripped before triage, which matters more than it sounds: leaving it in would make every message start with the same words and cluster them all onto the webhook's own name instead of onto what they are about.
The exact Request URL and any values you need to paste are shown on the Microsoft Teams card inside your project settings, because they are specific to your project. Full Microsoft Teams setup guide.
What FeedbackFlow reads from Teams
The message text with the bot mention removed, and who sent it. Nothing else in the payload is stored.
| Field | What FeedbackFlow does with it |
|---|---|
| text | The feedback item's text, with the leading @mention of the webhook stripped. |
| id | Deduplication key. A redelivered message is recognised rather than becoming a second item. |
| from.name | Attribution, so a topic can show who raised it. |
| from.id | Stored alongside the name so the same person is recognised across messages. |
What this looks like in practice
Someone posts in the channel without mentioning the webhook
Nothing happens. Teams only delivers messages that mention the webhook, which makes capture explicit rather than ambient.
A message is only the @mention with no text
Ignored. Stripping the mention leaves nothing to triage.
Three people relay the same customer complaint
One ranked topic with three requesters, not three items.
You delete the webhook
The flow stops immediately. Existing items stay.
Limits worth knowing
What this connector does not do, so you can find out here rather than after you have wired it up.
- Every message has to @mention the webhook. Unlike Slack, Teams will not forward ordinary channel messages, so nothing is captured passively.
- Outgoing webhooks are per team, not per channel, and are subject to whatever your tenant allows. Some organizations disable them.
- No email address is captured, because Teams outgoing webhooks do not include one. These items cannot be weighted by account value.
- Attachments, cards, and reactions are not captured. Only the message text.
Frequently asked questions
- Why do I have to mention the webhook every time?
- That is how Teams outgoing webhooks work: they only fire on messages that mention them. It is a real difference from Slack, where the app sees every message in a channel it has been invited to. The upside is that capture is deliberate, so a channel can hold ordinary conversation without all of it becoming feedback. The downside is that it only works if your team remembers, so it is worth agreeing on before you announce it.
- Do I need tenant admin to set this up?
- Usually not. Creating an outgoing webhook needs team ownership rather than tenant administration, so a team owner can normally do it alone. Some tenants disable outgoing webhooks entirely, though, in which case the Connectors menu will not offer the option and you will need someone in IT to enable it.
- Is the security token verified, or just stored?
- Verified on every request. Teams signs the raw request body with HMAC-SHA256 and sends it in the Authorization header prefixed with HMAC. FeedbackFlow recomputes that signature and compares it in constant time, so a request with no signature or the wrong one is rejected before anything is parsed.
- Can I use this for internal feedback rather than customer feedback?
- Yes, and it is often the better fit. Teams is where your own staff relay what customers told them, which is feedback that otherwise never gets written down anywhere countable. Those items rank alongside direct customer feedback, so a problem five salespeople keep hearing shows up with five requesters behind it.
Connect Microsoft Teams today
Free plan. No credit card. Live in 2 minutes.