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 Teams through the Workflows app’s webhook trigger. Microsoft deprecated the old Office 365 Connectors in 2024, so Workflows is the supported path now.

​
Before you start

  • You can add a workflow to the target Teams channel.
  • You have a Microsoft 365 account on any paid tier (E1, E3, E5, Business Basic, or Business Standard).
The workflow runs on the Power Platform and counts against your tenant’s flow quota. At uptime-alert volume that’s a non-issue.

​
1. Create the workflow in Teams

1

Open the target channel

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

Open Workflows

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

Pick the webhook template

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

Sign in and add it

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

Copy the URL

Workflows returns a long URL like https://prod-NN.region.logic.azure.com:443/workflows/.../triggers/manual/paths/invoke?.... Copy the whole thing.
The URL is long because it carries the workflow ID and signing parameters in the query string. Every character matters, so paste it intact.
The Workflow URL is a credential. Anyone who has it can post Adaptive Cards into your channel. If it leaks, delete the workflow in the Teams Workflows panel and recreate it.

​
2. Add the channel in Tallwatch

1

Open the channels page

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

Pick Microsoft Teams

Choose the Microsoft Teams kind and name it for the audience, like Teams #incidents.
3

Paste the URL and test

Paste the Workflow URL into Incoming webhook URL, click Save, then Send test alert. The card should appear in Teams within a few seconds.

​
What the alert looks like

An Adaptive Card with:
  • The monitor name and incident status in the header
  • Failing regions, duration, and severity as fact rows
  • An Open in Tallwatch button linking to the incident
Teams renders the card the same way across desktop, web, and mobile.

​
Troubleshooting

The workflow may be paused. In Teams, open … → Workflows, find yours, and confirm it shows Enabled. If the system disabled it after a failure, click Repair, then Enable.
The URL was truncated (common when copying from a narrow window) or the workflow was 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 strips it down, Microsoft changed the wrapping. Open an issue and we’ll match the new shape.
Connectors were deprecated in 2024. The Workflows webhook above is the replacement. Set up the new path and delete the old connector.

​
Reference

PropertyValue
Channel kindteams
Required configwebhook_url (the Workflow URL)
DeliveryImmediate, no proactive rate limit; Teams enforces its own
RetryUp to 3 inline attempts on 5xx, 429, network, or timeout, then failed
Outbound to*.logic.azure.com