Microsoft Teams Integration
Send Convor notifications to a Microsoft Teams channel with a Power Automate Teams Workflows webhook.
Warning
Microsoft Teams integration requires a Microsoft 365 work or school account. Personal Microsoft accounts (hotmail.com, outlook.com) cannot create the required Power Automate Teams workflow.
The Microsoft Teams integration sends Convor notifications to a Teams channel using a Power Automate Teams Workflows webhook. New conversations, messages, and status changes appear in your channel, keeping your team informed without leaving Teams.
Prerequisites
- A Microsoft 365 work or school account
- A Microsoft Teams team and channel where you can add workflows
- Access to Power Automate in the same Microsoft 365 tenant
- Convor Growth plan or higher
Getting Your Webhook URL
Microsoft retired the older Office 365 connector flow for new Teams webhooks. Use the Power Automate Teams Workflows trigger instead:
- Open Power Automate with your Microsoft 365 work or school account.
- Create a new automated cloud flow.
- Use the Microsoft Teams webhook trigger named When a Teams webhook request is received.
- Set Who can trigger the flow? to Anyone.
- Add the Microsoft Teams action Post message in a chat or channel.
- Configure the action to post as the Flow bot, post in a channel, and select your target team and channel.
- In the message field, use the incoming request body text value. In Power Automate expression syntax, this can be:
@{coalesce(triggerBody()?['text'], string(triggerBody()))}- Save the flow, then copy the generated HTTP POST URL. The full URL must include the
sp,sv, andsigquery parameters.
Setup
In your Convor dashboard, open Integrations → Teams. Paste the webhook URL, set the channel name for reference, choose which events should trigger notifications, and save the configuration.
{
"integration": "teams",
"webhookUrl": "https://...environment.api.powerplatform.com/.../triggers/manual/paths/invoke?api-version=1&sp=...&sv=1.0&sig=...",
"channelName": "convor-support",
"events": [
"new_conversation",
"new_message",
"conversation_assigned",
"sla_breach",
"ai_handoff"
]
}Configuration Options
| Option | Description |
|---|---|
| webhookUrl | The full Power Automate Teams Workflows HTTP POST URL, including the sig query parameter |
| channelName | A display name for reference in Convor (does not affect delivery) |
| events | List of Convor events that trigger Teams notifications |
Supported Events
| Event | Description | Status |
|---|---|---|
| new_conversation | A visitor starts a new chat session | Supported |
| new_message | An unread message arrives in an active conversation | Supported |
| conversation_assigned | A conversation is assigned to an operator | Supported |
| sla_breach | Response time exceeds the configured SLA threshold | Supported |
| ai_handoff | The AI bot transfers a conversation to a human operator | Supported |
Troubleshooting
Warning
If notifications are not appearing in Teams, verify the Power Automate flow is enabled and the copied URL includes the sig query parameter.
- Webhook URL invalid: Copy the full HTTP POST URL from the Power Automate trigger. A URL without
sp,sv, andsigwill return an authorization error - Flow not running: Confirm the flow is turned on and that the trigger is set to Anyone
- Message body is empty: Check that the Teams action message uses
triggerBody()?['text']or thecoalesce(...)expression shown above - Admin permissions required: If Power Automate or Teams Workflows is blocked, contact your Microsoft 365 admin to enable it for your tenant
- Notifications delayed: Teams webhook delivery can take up to 30 seconds under normal conditions
Was this page helpful?