Teams workflow webhook tester
Paste a Teams workflow’s webhook URL to check that it’s the right kind, send one sample card, and see what Microsoft answers.
It runs in your browser. Your workflow URL goes straight to Microsoft’s workflow service and nowhere else: this site never sees it, and nothing is saved. Treat the URL like a password: anyone who has it can post to your channel. If it leaks, delete the workflow and make a new one.
How to check a workflow
- In Teams, open the channel that should get the messages, choose ••• beside its name, then Workflows.
- Choose the template “Send webhook alerts to a channel,” check the team and channel, and choose Save.
- Copy the webhook URL Teams shows. It contains powerplatform.com (older ones, logic.azure.com).
- Paste it here and press Send a card. Teams posts one card in that channel, and this page shows Microsoft’s answer.
If the check fails
- The URL contains webhook.office.com
- That’s a retired Office 365 connector. Make a workflow from “Send webhook alerts to a channel” instead.
- Microsoft says WorkflowNotFound
- The workflow was deleted, or the URL came from another one. Open it under ••• → Workflows → Your workflows and choose Copy webhook link.
- Microsoft answers 202, but no card shows up
- The workflow got the card but didn’t post it. Check its run history. A workflow built from the bare webhook trigger, not the template, accepts the card and posts nothing.
- Microsoft asks for a sign-in
- The workflow came from a template that makes posters sign in. Use “Send webhook alerts to a channel.”
- The card went to the wrong channel
- Each workflow posts to the channel picked when it was saved. Make a new workflow for the channel you want.
Example card
A Teams workflow posts only an Adaptive Card. This is the card Fwrd sends, as your own code would send it:
{
"type": "message",
"attachments": [
{
"contentType": "application/vnd.microsoft.card.adaptive",
"contentUrl": null,
"content": {
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.4",
"body": [
{
"type": "RichTextBlock",
"inlines": [
{
"type": "TextRun",
"text": "Your sign-in code is 482913"
}
]
}
]
}
}
]
}A short card from a terminal, with your workflow’s URL:
curl -X POST -H "Content-Type: application/json" \
-d '{"type":"message","attachments":[{"contentType":"application/vnd.microsoft.card.adaptive","contentUrl":null,"content":{"type":"AdaptiveCard","version":"1.4","body":[{"type":"TextBlock","text":"Hello from my workflow"}]}}]}' \
"<your workflow URL>"- The workflow posts only an Adaptive Card. Plain {"text": …} is accepted with a 202 and never shows up.
- A 202 means the workflow has the request, not that the card was posted; the run history says what happened next.
- Keep the whole URL, sig= part included, and quote it in a terminal: it contains & characters.
Sending your iPhone’s texts to this channel
I built this for Fwrd, my iPhone app that forwards the texts you choose to a Teams channel, such as sign-in codes or alerts. It sends the same bare card as this page. Paste this workflow URL into Fwrd’s Microsoft Teams destination, and texts arrive in the channel on their own. The Teams setup guide walks through the rest, and forwarding iPhone SMS to Teams shows what it’s for.
Fwrd on the App Store: free for 15 forwards a month.