Connect Microsoft Teams to Your Playbooks
Henneth sends messages to your Microsoft Teams channels via incoming webhooks, so your team gets real-time alerts and reports from playbook actions. This guide walks you through creating a Teams webhook and connecting it to Henneth. Setup takes about 5 minutes.
Prerequisites
- A Microsoft Teams workspace where you have permission to manage channel connectors (or can request it from a Teams admin)
- The Teams channel(s) you want Henneth to post to
- Access to your Henneth dashboard (Enterprise plan)
Create an incoming webhook in Microsoft Teams
Microsoft Teams supports incoming webhooks through Power Automate workflows (the modern approach) or legacy Office 365 connectors. We recommend using Power Automate workflows.
Using Power Automate (recommended):
- 1.Open Microsoft Teams and navigate to the channel you want Henneth to post to
- 2.Click the + (Add a tab) button, or go to Power Automate (make.powerautomate.com)
- 3.Create a new Instant cloud flow with the trigger When a HTTP request is received
- 4.In the trigger settings, set the method to POST and define a JSON schema (or leave it open to accept any JSON)
- 5.Add an action: Post message in a chat or channel — configure it to post to your target channel
- 6.Save the flow. Power Automate will generate a webhook URL
The generated URL will look like:
Copy this URL. You'll need it in Step 2.
Webhook URL security
The Power Automate webhook URL contains authentication tokens embedded in the URL itself. Treat it like a password — do not share it publicly or commit it to repositories.
Add the connection in Henneth
Log in to your Henneth dashboard and navigate to Settings → Integrations.
Scroll to the Connections section and find Microsoft Teams with the description: "Send messages to Microsoft Teams channels via incoming webhooks."
Click + Add Connection and fill in the following fields:
Test and save
Click Test Connection to send a test message to your Teams channel. Check your Microsoft Teams workspace — you should see a test message from Henneth in the target channel.
If the test succeeds, click Save to store the connection.
If the test fails, verify that:
- The webhook URL is correct and complete (Power Automate URLs are long — make sure you copied the entire string)
- The Power Automate flow is turned on and active
- The target channel still exists in Teams
- Your Power Automate license/plan supports HTTP request triggers
Use Teams in playbooks
Once saved, your Microsoft Teams connection is available as a destination in Henneth playbooks. You can configure playbook actions to:
- Send alerts — when AI visibility scores change significantly
- Post reports — with periodic performance summaries to a channel
- Notify your team — when new AI agent crawl patterns are detected
- Trigger notifications — based on audit findings or content recommendations
Each playbook action lets you select which Teams connection to use, so you can route different types of messages to different channels.
Managing connections
Multiple connections — You can create as many Teams connections as you need. Each connection points to a different webhook URL and can target a different channel.
Editing — Click on an existing connection to update its name or webhook URL.
Deleting — Click the delete icon next to a connection to remove it. Any playbooks using that connection will need to be updated with a new destination.
Security best practices
Webhook URL confidentiality
Your Power Automate webhook URL contains embedded authentication tokens. Anyone with the URL can trigger the flow and post messages to your channel. Do not commit it to public repositories or share it in public channels.
Flow management
Regularly review your Power Automate flows at make.powerautomate.com. Disable or delete any Henneth-related flows you no longer use.
Channel access
Consider using a dedicated channel for Henneth notifications rather than posting to general-purpose channels. This makes it easier to manage permissions and audit message history.
Credential storage
Webhook URLs are encrypted at rest using AES-256 encryption in Henneth. They are never logged in plaintext and are only decrypted when sending messages to Teams on your behalf.
Token expiration
Power Automate webhook URLs may expire based on your organization's policies. If messages stop delivering, check whether the flow is still active and regenerate the URL if needed.
Next steps
- Permissions — understand exactly what Henneth can and cannot access
- Troubleshooting — fix common issues with webhook delivery and message formatting