Workflows for Teams (Webhook-style)
If you don’t need a full Bot identity or Direct Message capabilities, then you can support a simplified, channel-only integration using Workflows for Microsoft Teams. This approach relies on a unique Webhook URL generated by the Teams client. It requires no Azure app registration and no administrator consent.User generates the webhook URL (Teams client)
The setup begins inside the Microsoft Teams app. Instruct your users to follow these steps:1
Open Workflows
In Microsoft Teams, go to Apps in the sidebar.
Search for and open Workflows.
2
Create a new flow
Start from a blank flow or use a template.
3
Choose a trigger
For example, select When a Teams webhook request is received.
4
Add a post message action
Add an action to post a message into a specific channel.
5
Save the workflow
Publish your changes so the Teams workflow can receive events.
6
Copy the webhook URL
Once created, the workflow generates a unique URL. The user must copy this URL.
Register the webhook endpoint (Novu)
Unlike the Bot integration, you don’t usems_teams_channel here. Instead, you treat this as a generic webhook endpoint. Your app should provide a form where the user can paste the URL they generated in the previous step.
- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
Sending the notification
When you trigger a workflow that targets this subscriber:1
Novu sends HTTP POST
Novu sends a standard HTTP POST payload to the Teams Workflow URL.
2
Workflows receives payload
3
Workflow posts message
The Workflow runs and posts the message content into the configured channel.
Related
MS Teams overview
Compare the bot, webhook, and agent paths.