Connect Microsoft Teams: step-by-step guide
Posts the run summary to a Teams channel, and with NEXUS_TEAMS_NOTIFY=true one message per failing test. This guide takes you from nothing to a verified connection, and lists the errors you can meet with their cause and fix.
Last updated:
Keep your credentials private. Never paste a token, key, password or webhook URL into a chat. Type it only in Studio → Settings → Integrations, where it is saved in your workspace's .env file and shown as dots. The same goes for an AI assistant: it can walk you through this guide, but it never needs your token.
What you need
- A Teams channel where you can add a workflow.
- One Workflows webhook URL for that channel.
Get the credentials
- In Teams, open the channel's ··· menu → Workflows and add "Post to a channel when a webhook request is received".
- Copy the webhook URL it gives you. It ends in logic.azure.com (older connectors: webhook.office.com). The URL is itself the secret.
- Keep it in your clipboard. Do not paste it anywhere except the Studio (next step).
Connect it in the Studio
- In the Studio, open Settings → Integrations → Microsoft Teams.
- Paste the webhook URL and press Save & send test. A test message goes to the channel.
- Turn on
TEAMS_ENABLED. For one message per failing test, also turn onNEXUS_TEAMS_NOTIFY.
Check that it works
- Send test message answers "Sent." and the message appears in the channel.
- Run any test. The run summary arrives in the channel.
Common errors
| What you see | Cause | Fix |
|---|---|---|
| "No webhook" | TEAMS_WEBHOOK_URL is empty. | Paste the webhook URL in Settings → Integrations and save. |
"TEAMS_WEBHOOK_URL is not a Teams webhook" | The value is not an https URL on logic.azure.com or webhook.office.com. | Copy the URL again from the workflow's "Post to a channel when a webhook request is received" trigger. |
| An HTTP 4xx or 5xx answer from Teams | The workflow was turned off or deleted, or its owner left or lost the license, so it no longer runs. | Open the workflow in Teams (Workflows → manage), turn it on or create a new one, and save the new URL. |
| "could not reach Teams (ENOTFOUND)" or "did not answer within 20 s" | This PC cannot reach Microsoft: a VPN or proxy, or no network. | Check the network from the same PC and retry. |
| The test works but failures do not post | TEAMS_ENABLED is false, or only the run summary is on: per-test messages need NEXUS_TEAMS_NOTIFY=true. | Turn on both switches. |
Settings keys
| Key | What it does | Valid value | How to check it |
|---|---|---|---|
TEAMS_ENABLED | Send alerts to Microsoft Teams | true or false | Turn on after the test message arrives. |
TEAMS_WEBHOOK_URL | Teams channel for alerts (secret, saved only on this computer) | An https://…logic.azure.com or …webhook.office.com URL | Send test message posts to the channel. |
NEXUS_TEAMS_NOTIFY | Teams alert per failure | true or false | One message per failing test arrives, not only the run summary. |
More: all integrations, the Settings guide, troubleshooting. Other guides: Jira Cloud, Azure Boards, Slack, Telegram, GitHub Issues.
Still stuck? Write to [email protected] with the exact error line the Studio shows. Do not include a token.