Reply to Outlook Email: Microsoft Outlook 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
Message ID messageId	string	Required	Message ID
Reply Body comment	html	Required	Reply Body. e.g. "<p>Thanks for your email...</p>"

Sample request

{
  "messageId": "{{trigger.messageId}}",
  "comment": "<p>Thanks for your email...</p>"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Reply to Outlook Email.

What does the Reply to Outlook Email action do in Microsoft Outlook?

Replies to a specific message preserving the thread. For "auto-acknowledge support emails" or "AI-generated reply approved → send" workflows.

What inputs does Reply to Outlook Email require?

Required: Message ID, Reply Body. 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 Outlook 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 Outlook Email support batch operations?

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

More actions