How it works
- Create a webhook in Teams. In Teams, add a Workflows flow from the “When a Teams webhook request is received” template for the channel you want, and copy its URL.
- Paste it into Crumb. An admin pastes the URL under Microsoft Teams in Settings → Integrations. Crumb accepts https URLs on Teams' webhook hosts: logic.azure.com for Workflows, or webhook.office.com.
- Send a test card. Send test posts a sample card, so you can check the channel before anything real arrives.
- Cards arrive as things happen. Crumb posts a card when new feedback is created, whether it came from the widget, Compose,
/crumbin Slack, or a feedback source; when a customer replies; and when an item's status changes, including when a customer closes it. Reply and status cards include an Open button that links to the thread. - Customers can get their own. Each account can have its own Teams webhook too, so the customer's team sees your replies, status changes, and roadmap updates in their channel.
What syncs
| What | Direction | When |
|---|---|---|
| New feedback | Crumb → Teams | When an item is created |
| Customer replies | Crumb → Teams | When a customer replies, with the first 280 characters |
| Status changes | Crumb → Teams | On every change, with the reason if you gave one |
| Replies, status, roadmap updates for one account | Crumb → that customer's channel | Through the webhook the account's admin set in the widget |
| Anything from Teams | Not synced | The webhook is one-way, so nothing comes back into Crumb |
Updates in your customers' Teams
A customer's account admin pastes a Teams webhook URL into the Admin tab of the widget. Your replies (never internal notes), status changes, and roadmap updates for initiatives that account follows then post to their channel alongside the usual emails. Customers on Slack can use an incoming webhook the same way; see Crumb for Slack.
Setup
Crumb Cloud: an admin pastes the webhook URL under Microsoft Teams in Settings → Integrations. There's no OAuth step and no app to approve in your Microsoft tenant.
Self-hosted: identical, with no app registration and no environment variables. If you need to post through an internal bridge instead of Teams' own hosts, set CRUMB_WEBHOOK_ALLOW_ANY=1 to lift the host allowlist.
Frequently asked questions
Do I need to install a Teams app?
No. Crumb posts to a webhook URL from a Teams Workflows flow, so there's nothing to install in Teams.
Can Crumb send direct messages in Teams?
No. Teams support posts cards to one channel per workspace, so everyone in that channel sees the same cards. Personal DMs for replies and mentions are a Slack feature.
Can my customers get updates in their own Teams?
Yes. Each account can have its own Teams or Slack webhook, set by the customer's account admin in the widget. They get your replies, status changes, and roadmap updates.
What happens if the webhook stops working?
Posting is best-effort: Crumb tries each card once, and a failed post never blocks or loses the feedback itself. Send test confirms the connection, and an admin can paste a new URL anytime.