Skip to content
CommunicationReal-timeUpdated May 2026

Microsoft Teams

Microsoft Teams channels and messages into workflows

Microsoft Teams is the comms layer for most organizations running on Microsoft 365, the equivalent of Slack's role in non-Microsoft shops. Two triggers cover the activity Teams workflows actually want to act on: Message Received (a new message in a channel you've authorized) and Channel Created (a new channel appears in a team). Nine actions handle the operational surface: Send Channel Message (with adaptive cards or plain markdown), Reply to Message (in-thread reply), Delete Message, Get Message, Create Channel, List Channels, List Teams, List Team Members. The integration authorizes via Azure AD OAuth, with the Tiny Command app scoped to read/write the channels you grant access to (admin consent may be required depending on your tenant's settings). Common patterns: a Microsoft Dynamics opportunity stage change pings the AE in a Teams channel via Send Channel Message with an adaptive card showing the deal details, or a Linear bug filed against a customer creates a Teams channel for the incident and adds the relevant stakeholders.

2triggers
9actions
≈ 2 minto set up
Freetier · no card
Triggers

Workflows start when Microsoft Teams does.

2 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven
Actions

Do anything Microsoft Teams can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

ActionWhat it does
Create Teams ChannelCreates a new channel under a team with name, description, type (standard, private, shared). For "new project → auto-create dedicated channel" workflows.
Delete Teams MessageRemoves a message. For "cleanup bot-posted ephemera" or compliance "delete sensitive accidentally-posted content" workflows.
Get Teams MessageReturns a specific message with author, body, reactions, replies. For analysis or archival workflows that need richer message context.
List Teams ChannelsReturns channels in a team. Useful for resolving channel IDs at workflow setup.
List Teams MembersReturns members with role (owner, member). Useful for "alert team owners" or for team-roster sync workflows.
List TeamsReturns teams the connected user is a member of. The base lookup for multi-team workspaces.
Reply to Teams MessagePosts a reply inside an existing thread. For "all updates about this incident → same thread" patterns that contain noise.
Send Teams Channel MessagePosts a new message to a specific channel with optional rich content (Adaptive Cards). The base hook for "external event → post to team channel" workflows.
Update Teams MessageEdits a previously-posted message. For "status-update bot that edits its own message as state changes" workflows that keep the channel clean.
Recipes

Pre-built Microsoft Teams workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Microsoft Teams once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Microsoft Teams field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Microsoft Teams integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Microsoft Teams to Tiny Command?
Open the Tiny Command workflow builder, drop in a Microsoft Teams node, and click Connect. Authorize Microsoft Teams once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.
What Microsoft Teams triggers does Tiny Command support?
Tiny Command supports 2 real-time Microsoft Teams triggers, including "Teams Channel Created", "Teams Message Received". Each trigger fires within seconds of the event happening in Microsoft Teams.
What Microsoft Teams actions can I run from a workflow?
9 Microsoft Teams actions are available out of the box, covering communication operations like "Create Teams Channel". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.
Is the Microsoft Teams integration real-time?
Yes. Teams Channel Created and every other Microsoft Teams trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Microsoft Teams rather than on a polling schedule.
Do I need to write code to use Microsoft Teams with Tiny Command?
No. Every Microsoft Teams trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Microsoft Teams API endpoint directly.
How much does the Microsoft Teams integration cost?
There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Microsoft Teams integration itself has no per-app surcharge.
Related

More communication apps people connect.

Same category as Microsoft Teams, ordered by how often teams pair them. Hover the carousel to pause.

Do more with Microsoft Teams.

Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.