Posting to Microsoft Teams with workflows

Does your team work in Microsoft Teams? A workflow can post a message in a Teams channel, for example when your AI agent finds a lead or a chat needs a follow-up.

tawk.to has no Teams step, so you connect the two yourself. In Teams, you create a workflow that receives messages. In tawk.to, an HTTP request step sends them. You copy a URL and a short message template, and you do not write code.

Time: about 20 minutes.

Note: Microsoft retired the old Incoming Webhook connector for Teams in May 2026. Use the Workflows app in Teams, as in this guide.

1. In Teams, go to the channel for your alerts.
2. Next to the channel name, click More options (…).
3. Click Workflows.
4. Search for and select the Send webhook alerts to a channel template.
5. Follow the steps on the screen. Check that the team and channel are correct, then save the workflow.
6. Copy the webhook URL that Teams shows.

Important: Anyone who has this URL can post to your channel. Keep it private.

The Teams workflow belongs to the person who created it. If that person leaves your company, the alerts can stop. To prevent this, add a colleague as a co-owner of the workflow in Power Automate.

For more, see Microsoft's guide Send messages in Teams using incoming webhooks.

1. Open your workflow in Automations > Workflows.
2. Click Add step.
3. Click Action.
4. In Category, select Developer tools.
5. In Action, select HTTP request.
6. In URL, paste the URL from Teams.
7. In Method, select POST.
8. In JSON body, paste the template below.
9. Change the text in the "text" lines to suit your alert.
10. Click Save.

You do not need any Headers. tawk.to sends the body as JSON.

Each TextBlock is one line in the Teams message. To add a line, copy a TextBlock line and change its text. Put a comma between lines, but not after the last one.

Note: The JSON body must be valid JSON, or you cannot save the step. Keep each {{ }} value inside quotation marks, as in the template. tawk.to inserts the details safely, even when they contain quotation marks or line breaks.

Why chats need an AI step: the visitor's name, email address and chat messages are private details. An HTTP request cannot send them, because only Slack steps and conditions can use them. An AI step can read them, though. Ask it for a short summary with the name, email address and need, then put its output in the message.

The quickest start is the Qualified lead hand-off template. Your AI agent already collects the name, email address and need there, and the template above uses those details. Delete the template's Send Slack notification step and add the HTTP request step in its place.

For every detail you can use, see Using runtime data in workflows.

1. In the Settings tab, turn on Enabled and click Save.
2. Click the Runs tab.
3. Click Run now.
4. In Trigger data (JSON), change the sample values to a test name and email address.
5. Click Run now.
6. Check your Teams channel for the message.
7. Click the run to see the HTTP status.

A status from 200 to 299 means that Teams accepted the message.

Important: Run now starts a real run, so every step runs. A test of Qualified lead hand-off, for example, also creates a real deal.

By default, any status outside 200 to 299 fails the step and stops the run. If later steps should still run, turn on Continue even if the request fails in the step. Later steps can then check the HTTP status.

For more about runs and errors, see Testing, monitoring and troubleshooting workflow runs.

Have a question we haven't covered or need support?

• Chat with us (live chat is available 24/7)
• Visit our Feedback page
• Schedule a call with us