Guide · Verified November 17, 2026

Microsoft Teams target guide

Short answer: A Hooks Microsoft Teams destination POSTs a MessageCard to an incoming webhook URL from an Office 365 Connector, Power Automate, or Workflows; the URL is a project secret. Connectors answer 200 with the body 1, and Workflows answer 202.

Teams accepts a small card schema, not arbitrary HTML: a title, a text body with a limited markdown subset, and an accent color. The destination builds that card from the event, keeps the rejection reason Teams returns, and shows the card it sent in the delivery log.

1. Create the incoming webhook

In the target channel, open Workflows and create the “Post to a channel when a webhook request is received” flow, or add the Incoming Webhook connector. Copy the generated URL; it is accepted only when it uses https and points at *.webhook.office.com, *.logic.azure.com, or *.environment.api.powerplatform.com.

2. Store the URL as a project secret

Settings → Security → Project secrets → add TEAMS_WEBHOOK_URL. The config references it as {{secret.TEAMS_WEBHOOK_URL}}; a literal URL is rejected at save time, and a URL on any other host or without https fails with INVALID_TEAMS_WEBHOOK_URL before anything is sent.

Destination config

{
  "webhookUrl": "{{secret.TEAMS_WEBHOOK_URL}}",
  "title": "New {{event.type}}: {{event.subject.title}}",
  "text": "{{event.subject.url}}",
  "themeColor": "0076D7"
}

3. Write the card templates

`title` defaults to the event subject title and `text` to its URL; both render with the same template engine as every target. Teams renders a small markdown subset in `text` (bold, links, lists) and no HTML. `summary` is required by connectors, so Hooks fills it with the title, falling back to the text. A card whose title and text both render empty fails with EMPTY_TEAMS_MESSAGE. themeColor is six hex digits without the leading #.

Request Hooks sends

POST https://acme.webhook.office.com/webhookb2/<token>
Content-Type: application/json

{
  "@type": "MessageCard",
  "@context": "https://schema.org/extensions",
  "summary": "New issues.opened: Login fails on Safari",
  "title": "New issues.opened: Login fails on Safari",
  "text": "https://github.com/acme/app/issues/7",
  "themeColor": "0076D7"
}

4. Read the response and retries

An Office 365 Connector answers 200 with the plain body 1, and a Workflows webhook answers 202; both are successes. Other statuses extract message, errorMessage, or error.message from the JSON body and append it to the HTTP error, so an expired webhook is visible in the attempt. 408, 425, 429, and 5xx retry; 3xx is blocked as REDIRECT_BLOCKED. Send a test event from the endpoint to verify the connector; the delivery log shows the status and any reason Teams returned.

Frequently asked questions

Connector or Workflows webhook?

Both work. The classic Incoming Webhook connector is the quickest, while a Workflows flow lets you post to channels that disable connectors. Hooks accepts either URL and sends the same MessageCard.

Why does my HTML show up as plain text?

Teams renders a small markdown subset and ignores HTML. Use markdown links and bold instead, or send the card through a generic webhook destination if you need a richer Adaptive Card.

What is the summary field for?

Teams connectors require it. Hooks sets summary from the title and falls back to the text, so a card with an empty title still renders.

Why did the delivery fail with INVALID_TEAMS_WEBHOOK_URL?

The URL in the secret was not https or its host did not end with one of the Teams incoming-webhook suffixes. Copy the URL straight from the channel's connector or Workflows flow.

Reference

Keep going

Trigger AI agents from webhooksPoint the provider's webhook at a Hooks endpoint, add one destination per agent target with filters and a task template, and every matching event becomes an agent task with retries and a delivery log.Grok Bot target guideA Hooks destination POSTs one JSON task to your Grok Bot routine URL with a Bearer key; a 2xx means the task was queued. Configure the routine URL and key once, then map event fields into the task template.T3 Code target guideA Hooks destination POSTs JSON to your T3 Code task's On a webhook URL; T3 Code answers 202 when the agent run is accepted. Keep the URL (it carries a token) in a project secret and sign the body when the task requires it.Paseo target guideA Hooks destination POSTs one manual-run dispatch to Paseo Hub (on: manual.run) with project, trigger, actor, and rendered input. Hub answers 200 with a triggerRunId that Hooks records on the delivery.Slack target guideA Hooks Slack destination posts either to an incoming webhook URL already bound to a channel, or to chat.postMessage with a bot token and channel id so one app can reach many channels.Discord target guideA Hooks Discord destination POSTs a message to a channel's incoming webhook URL; that URL carries the token, so it lives in a project secret. Content is plain text with optional embeds, and Discord answers 204 when the message is accepted.Telegram target guideA Hooks Telegram destination calls sendMessage with your bot token and a chat id; the token stays in a project secret. The message text renders from the event, and Telegram's ok flag decides success even when the HTTP status is 200.Lark target guideA Hooks Lark destination posts a text message to a group's custom bot webhook on open.larksuite.com. The URL is a project secret, and when the bot's signature check is on, Hooks adds the timestamp and HMAC-SHA256 signature the bot requires.