# Teams workflow webhook tester

Canonical page: https://www.fwrdsms.com/tools/teams-webhook-tester

Paste a Microsoft Teams workflow webhook URL (from the “Send webhook alerts to a channel” template) on the page to check it and send one sample Adaptive Card, and see Microsoft’s answer. 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

1. In Teams, open the channel that should get the messages, choose ••• beside its name, then Workflows.
2. Choose the template “Send webhook alerts to a channel,” check the team and channel, and choose Save.
3. Copy the webhook URL Teams shows. It contains powerplatform.com (older ones, logic.azure.com).
4. Paste it here and press Send a card. Teams posts one card in that channel, and this page shows Microsoft’s answer.

Microsoft answered 202: the workflow has the card. It shows up in the channel within a minute or so. If it doesn’t, open the workflow’s run history in Teams (••• → Workflows → Your workflows) to see which step stopped.

## 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

```json
{
  "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"
              }
            ]
          }
        ]
      }
    }
  ]
}
```

```bash
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

Fwrd is an iPhone app that forwards the texts you choose to a Teams channel through a workflow like this one, such as sign-in codes or alerts. It sends the same bare card as this page. Paste the workflow URL into Fwrd’s Microsoft Teams destination. Setup guide: https://www.fwrdsms.com/guides/microsoft-teams
