Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tallwatch.com/llms.txt

Use this file to discover all available pages before exploring further.

Tallwatch posts an Adaptive Card to your Teams channel using the Workflows app’s webhook trigger. This is the successor to the deprecated Office 365 Connectors and is the supported integration path going forward.

​
Before you start

  • You must have permission to add a workflow to the target Teams channel.
  • Workflows requires a Microsoft 365 account (any paid tier, including E1, E3, E5, Business Basic, Business Standard).
  • The workflow runs on the Power Platform and counts against your tenant’s flow quota — usually a non-issue at uptime-alert volume.

​
Step 1: Create the webhook workflow in Teams

1

Open the channel that should receive alerts

Navigate to the Teams channel (not the chat) where alerts should land. A dedicated incidents channel works best.
2

Open the Workflows menu

Click the … menu next to the channel name, then Workflows.
3

Pick the right template

Search for and pick Post to a channel when a webhook request is received.
4

Sign in and configure

Sign in with your Microsoft 365 account, confirm the team and channel, then click Add workflow.
5

Copy the webhook URL

Workflows returns a URL that looks like https://prod-NN.region.logic.azure.com:443/workflows/.../triggers/manual/paths/invoke?.... Copy it.
The URL is long because it embeds the workflow ID and signing parameters in the query string. Keep it intact when pasting — every character matters.
The Workflow URL is a credential. Anyone with it can post Adaptive Cards into your Teams channel. If it leaks, delete the workflow in the Teams Workflows panel and recreate it.

​
Step 2: Add the channel in Tallwatch

1

Open the channels page

Go to Settings → Alerts → Channels in the dashboard and click Add channel.
2

Pick Microsoft Teams

Select the Microsoft Teams kind. Name the channel for the audience: Teams #incidents or Platform team.
3

Paste the Workflow URL

Paste the long URL from the Teams Workflows screen into the Incoming webhook URL field.
4

Save and test

Click Save, then click Send test alert. The Adaptive Card should appear in your Teams channel within a few seconds.

​
What the alert looks like

An Adaptive Card with:
  • The monitor name and incident status as the card header
  • Key facts as fact-list rows: failing regions, duration, severity
  • A primary Open in Tallwatch action button that links to the incident detail page
Teams renders the card consistently across desktop, web, and mobile clients.

​
Troubleshooting

The Power Automate workflow may be paused. Open Teams → … → Workflows → find your workflow → confirm it shows as Enabled. If it failed and was disabled by the system, click Repair then Enable.
The URL is either truncated (often happens when copying from a small terminal window) or the workflow has been deleted. Recreate the workflow and paste the full URL.
The Workflow template wraps the request body in a specific shape. Tallwatch sends the canonical card; if Teams renders something stripped down, the wrapping changed on Microsoft’s side. File an issue with us — we will update the payload to match.
Microsoft deprecated Connectors in 2024. The Workflows webhook is the supported replacement. The setup steps above are for the new path.

​
Reference

PropertyValue
Channel kindteams
Required configwebhook_url (the Workflow URL)
Send rate limit1 per 30 s per channel (queued, not dropped)
Retry policyUp to 3 attempts on 5xx, then queued for the next 30-s slot
Outbound to*.logic.azure.com