How to Set Up Microsoft Teams Alerts with a TwoPulse Webhook

TwoPulse can send downtime, reminder, and recovery alerts to Microsoft Teams the same way it sends email and Slack. You create a webhook URL in Teams, paste it in Settings, and alerts post to that channel automatically.

Microsoft is moving Incoming Webhooks to Workflows (Power Automate). This guide uses that path. Legacy Office connector URLs still work in TwoPulse if you already have one.

What you need

• A Microsoft Teams channel where you have permission to add Workflows
• A TwoPulse account with access to Settings
• About five minutes

1. Create a Teams Workflows webhook

1. Open the Teams channel that should receive alerts
2. Click the ⋯ menu next to the channel name and choose Workflows (or Manage channel → Workflows, depending on your Teams client)
3. Search for Post to a channel when a webhook request is received
4. Select your team and channel, then create the workflow
5. When setup finishes, copy the HTTP URL (webhook URL). Keep it private—anyone with it can post to the channel

Official Microsoft help: Create incoming webhooks with Workflows for Microsoft Teams.

Your URL usually looks like:

https://prod-….logic.azure.com/workflows/…/triggers/manual/paths/invoke?…

Older connector URLs look like https://….webhook.office.com/webhookb2/…. TwoPulse accepts both.

2. Add the webhook in TwoPulse

1. Sign in to TwoPulse and open Settings
2. Find the Microsoft Teams card
3. Enter a short name (for example Ops channel or #alerts) so you can tell webhooks apart later
4. Paste the Teams webhook URL
5. Click Add

The status badge turns Active when at least one webhook is enabled. You can add more than one channel, pause delivery with the toggle, or remove a webhook anytime without affecting email or Slack.

3. What alerts look like

When a monitored service crosses your failure threshold, TwoPulse posts a card to Teams with:

• Clear incident / reminder / recovered labeling
• Service name, endpoint, HTTP status, latency, and failure context
• Buttons that open the TwoPulse dashboard (incident or status view)

You also get scheduled reminder alerts while a service stays down, and a recovery message when health checks pass again.

Tips

• Use a dedicated alerts channel so noise stays out of day-to-day chat
• Name each webhook clearly if you send the same account to multiple channels
• Treat the URL like a secret—rotate the workflow if it leaks
• Keep at least one Teams webhook enabled if you rely on Teams for paging; TwoPulse won’t let you disable the last remaining one while others still exist in the list

Troubleshooting

• Invalid webhook URL — Use an HTTPS Teams Workflows (logic.azure.com) or Office connector (webhook.office.com) URL, not a Slack or generic HTTP endpoint
• No messages in Teams — Confirm the webhook is listed and enabled, the workflow is turned on, and your monitored service has actually crossed the alert threshold (and that Celery worker/beat are running in production)
• Workflow deleted or URL rotated — Create a new workflow, add the new URL in Settings, then remove the old entry

Next steps

Once Teams is connected, keep monitoring your services as usual. TwoPulse will deliver down, reminder, and recovery alerts to every enabled Teams webhook—alongside email and Slack if those are configured too.