Reply to Teams Message: Microsoft Teams action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Team ID teamId	string	Required	Team ID
Channel ID channelId	string	Required	Channel ID
Message ID messageId	string	Required	ID of the message to reply to
Reply Content content	string	Required	Reply Content. e.g. "Your reply..."

Sample request

{
  "teamId": "{{trigger.teamId}}",
  "channelId": "{{trigger.channelId}}",
  "messageId": "{{trigger.messageId}}",
  "content": "Your reply..."
}

Returns

{
  "id": "reply-123",
  "body": {
    "content": "Your reply...",
    "contentType": "html"
  },
  "from": {
    "user": {
      "displayName": "User"
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Reply to Teams Message.

What does the Reply to Teams Message action do in Microsoft Teams?

Posts a reply inside an existing thread. For "all updates about this incident → same thread" patterns that contain noise.

What inputs does Reply to Teams Message require?

Required: Team ID, Channel ID, Message ID, Reply Content. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Microsoft Teams returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Reply to Teams Message support batch operations?

Yes. Run Reply to Teams Message inside a Loop node to process arrays. Tiny Command handles Microsoft Teams's rate limits automatically so you don't have to throttle manually.

More actions