Pro plan. Microsoft Teams works through HTTP steps (and event rules that call a webhook), which are part of Pro and Agency (and the free trial). Anything you already have keeps working on every plan. See Plans and billing.
How it connects: a Teams Workflows webhook URL. Microsoft’s docs point to Workflows for incoming webhooks while the old Office 365 connectors are retired (Create incoming webhooks with Workflows). The card below follows the Adaptive Card format the template expects; check it with your template on the first test.
1. Create the workflow in Teams
In Teams, open Workflows, pick the template Post to a channel when a webhook request is received, choose the team and channel, and copy the URL it gives you. The URL holds its own key: keep it private.2. Add the step in Kerux
A contact who replies leaves the campaign (the When the contact replies box). In that box, add Send to another campaign and pick a one-step “Replied: tell Teams” campaign. Its step is a Webhook / HTTP step with no connection:202 Accepted and posts the card.
For booked meetings, start a small campaign with the Meeting booked Kerux event and post {{meeting.start}} and {{meeting.title}} the same way.
Test with one contact
In the one-step campaign’s Builder, click Test to open Test on one contact and check the channel.Common errors
202, but nothing appears in the channel
202, but nothing appears in the channel
The workflow accepted the request but couldn’t read the card. Open the flow’s run history in Teams (Workflows) to see why; usually the body isn’t the Adaptive Card shape the template expects.
401 or 404
401 or 404
The URL was copied incompletely or the workflow was deleted. Copy it again from the workflow.