Teams Notifications
The Teams Notifications page lets you push concorbit events (deals won, invoices paid, bugs reported, contracts expiring, etc.) into Microsoft Teams channels via incoming webhook connectors. Each webhook is independently configured with its own target channel and its own set of events, so you can route sales events to the Sales channel, failure events to the Dev channel, and so on.
URL: /settings/integrations/teams
Required permission: settings.tenant
How to get there
Go to Settings from the sidebar.
Open the Teams notifications card (under Integrations).
How to get a webhook URL from Teams
Before you can add a webhook here, you need the URL from Microsoft Teams.
In Teams, open the channel you want notifications posted to.
Click the ⋯ menu on the channel → Connectors.
Find Incoming Webhook in the list and click Configure.
Give the connector a name (e.g.
Concorbit Sales) and optionally upload a logo.Click Create.
Teams displays a URL starting with
https://outlook.office.com/webhook/...orhttps://yourcompany.webhook.office.com/.... Copy it.
This URL is the authentication token. Treat it like a password. Anyone with the URL can post to your channel.
Adding a webhook in concorbit
Click Add webhook in the top-right of the page header to reveal the inline form.
| Field | Notes |
|---|---|
| Name | A label you'll use to identify this webhook (e.g. Sales Channel, Dev Alerts). Only shown within concorbit. |
| Webhook URL | Paste the URL from Teams. Must start with https://. |
| Events | Tick the event types this webhook should receive (see below). |
Click Save webhook. The new webhook appears in the Configured webhooks list below the form (the list is sorted by name).
Event types
Each webhook subscribes to one or more of these events:
| Event | Fires when |
|---|---|
| Deal won | A deal is marked as won in the CRM. |
| Invoice paid | A payment is received against an invoice. |
| New signup | A new customer signs up (useful for tenants running self-serve signup). |
| Bug reported | A user submits a bug report via the in-app bug widget. |
| Test run completed | A scheduled test run finishes (QA / integration testing feature). |
| Backup failed | A scheduled backup job fails. |
| Payment failed | A payment retry on a subscription or invoice fails. |
| Contract expiring | A support contract is approaching its end date. |
You can subscribe a single webhook to multiple events, and you can have multiple webhooks firing on the same event (e.g. one for Sales channel, one for Ops channel).
Managing existing webhooks
The Configured webhooks section lists configured webhooks. Each row shows:
The webhook's Name and active/paused badge.
A truncated view of the URL (full URL not displayed for safety).
Coloured badges for each event it subscribes to.
Row actions:
Toggle switch: enable/disable the webhook. Disabling stops notifications without deleting the config, so you can quickly mute a noisy channel.
Test: sends a test notification to the channel immediately. Confirms the URL is valid and the channel is receiving. You should see a message arrive in Teams within seconds.
Delete: permanently removes the webhook.
What the notifications look like
Notifications arrive in Teams as rich message cards with a title, body, optional link back to the relevant concorbit page, and a facts table. Example:
Deal won
Acme Corp signed for £24,000 (Professional Services)View deal →
Facts Owner Sarah Smith Stage Won Closed 14 Apr 2026
Deal won, invoice paid, and the signup events include dollar/pound amounts; failure events include the error detail for quick triage.
Notes and gotchas
The webhook URL is the credential. Don't share screenshots of the URL or paste it into public channels. If it leaks, delete the webhook here and create a new connector in Teams.
Test first, trust later. After saving, click Test to confirm it actually reaches the right channel. Mistyped URLs silently fail at Teams's end with no error back to concorbit beyond "failed".
Rate limits. Microsoft Teams throttles incoming webhooks at roughly one message per second per connector. High-volume events (e.g. hundreds of test-run completions per hour) can hit the limit. Subscribe to fewer event types per webhook, or create multiple webhooks for the same channel.
Webhooks are one-way. concorbit posts to Teams; Teams does not post back. For full two-way Teams integration (Teams presence dots, etc.) see Microsoft 365.