Create Outlook Draft: 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
To to	email	Required	To. e.g. "recipient@example.com"
Subject subject	string	Required	Message subject line.
Body body	html	Required	Message body content. Plain text unless the API specifies HTML/markdown.
CC cc	string	Optional	CC
Importance importance	options	Optional	Importance. Options: Low, Normal, High

Sample request

{
  "to": "recipient@example.com",
  "subject": "e.g. Quick update",
  "body": "e.g. Hi there, thanks for reaching out.",
  "cc": "{{trigger.cc}}",
  "importance": "{{trigger.importance}}"
}

Returns

{
  "id": "draft123",
  "isDraft": true,
  "subject": "Hello"
}

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

FAQ

Questions about Create Outlook Draft.

What does the Create Outlook Draft action do in Microsoft Outlook?

Creates an email in the Drafts folder without sending. For "AI-generated reply suggestion → save as draft for user review" workflows.

What inputs does Create Outlook Draft require?

Required: To, Subject, 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 Create Outlook Draft support batch operations?

Yes. Run Create Outlook Draft 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