Skip to content
Routario Docs

Send Teams

Step · Stable

Post a card to a Microsoft Teams channel or person.

Posts a card to a Microsoft Teams channel. text is the message body; title is an optional bold heading above it. channel picks one of the destinations registered under Settings → Integrations → Microsoft Teams; leave it empty to post to the channel Teams was connected with. The card always renders bold, italics, bulleted/numbered lists and links; turn on format_markdown and # headings, GFM pipe tables, --- dividers and standalone alt images render as native card elements too. Requires Microsoft Teams connected under Settings → Integrations.

When to use

Section titled “When to use”

Use to inform a Teams channel from any trigger — a new lead landed, a batch finished, a deadline slipped. text and title both accept a {{ reference }} to upstream values. Set channel when a flow should report somewhere other than the default channel — a finance digest to #finance, an ops alert to #ops.

When not to use

Section titled “When not to use”

For email delivery use Send email; for in-app alerts use Send notification; for Slack workspaces use Send Slack. This is fire-and-forget — it cannot ask a question or wait for a reply; to ask a Teams user a question use Ask a person with channel: teams. If Teams is not connected, or channel names a destination that is not registered, the step fails with a clear error.

Inputs

Section titled “Inputs”

channel

Section titled “channel”

string · optional

Teams addresses a channel by its incoming webhook, so each channel is registered once in Settings and picked here. The step stores the channel’s internal key, not its name, so renaming the channel in Settings never breaks this step. A channel typed by hand resolves by key or by name. A destination may also be a person, in which case the card arrives as a direct message from the Routario bot. An unregistered channel fails the step rather than quietly posting to the default.

Example: finance

  • ✓ “ — empty posts to the default channel — what every flow did before destinations existed
  • ✓ finance — the key of a channel picked from Settings → Integrations
  • ✗ https://acme.webhook.office.com/webhookb2/… — this field takes a destination NAME, not a webhook URL — paste the URL once in Settings and name it here

text

Section titled “text”

string · required

The card body posted to Teams. Template refs pull in upstream values. Which channel it lands in is set by the channel field above; empty means the one Teams was connected with. The card renders bold, italics, - bullets, 1. numbered lists and links as they are. With format_markdown on, a # heading renders as a bold heading, a GFM pipe table (header row, then a |---|---:| separator row setting alignment) as a table, a lone ---/***/___ line as a divider, and a standalone alt line as an inline image (https only — anything else stays literal text). A table over 8 columns or 50 rows stays literal text, as does a card too big for Teams — keep summary tables, not full data dumps.

Example: New lead: {{ crm_lookup.name }} ({{ crm_lookup.email }}).

  • ✓ New lead: {{ crm_lookup.name }} ({{ crm_lookup.email }}). — a concrete alert with the specific lead inlined
  • ✓ ## Today | Task | Due | |---|---:| | Invoice ACME | 14:00 | — with format_markdown on, a heading and a real Teams table
  • ✗ Something happened, check the app. — no actionable detail — inline the specific fact so the reader does not have to go look it up

title

Section titled “title”

string · optional

A short bold heading above the message body. Leave empty for a plain card with no heading.

Example: New lead

  • ✓ New lead — short label that categorises the card at a glance
  • ✗ New lead: {{ crm_lookup.name }} arrived via the website form at {{ now }} and needs immediate manager attention — too long for a heading — put detail in the message body, keep the title to a few words

format_markdown

Section titled “format_markdown”

bool · optional

Render # headings, pipe tables, --- dividers and standalone image lines in the message as native card elements instead of literal text. Bold, italics, lists and links render either way. Turn on when the text is authored as ordinary Markdown (an agent digest, a report); leave off for plain alerts.

Outputs

Section titled “Outputs”
  • status
  • http_status
  • channel

Requires

Section titled “Requires”

the microsoft_teams integration

Auto-generated from the skill registry (load_skills()). Do not edit by hand.