- Integrations
- /
- Microsoft Outlook
- /
- Actions
- /
- Send Outlook Email
ActionMicrosoft OutlookUpdated May 2026
How do I send email via Outlook?
Short answer: Drop the "Microsoft Outlook → Send Outlook Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | string | Required | Recipient email (comma-separated for multiple) |
Subject subject | string | Required | Subject. Example: Meeting follow-up |
Body (HTML) body | string | Required | Body (HTML). e.g. "<p>Hi, thanks for the meeting.</p>" |
CC cc | string | Optional | CC. e.g. "cc@example.com" |
Importance importance | options | Optional | Importance. Options: Low, Normal, High |
Sample request
{"to": "recipient@example.com","subject": "e.g. Meeting follow-up","body": "<p>Hi, thanks for the meeting.</p>","cc": "cc@example.com","importance": "{{trigger.importance}}"}
Returns
{"id": "msg_mic_123","status": "sent","success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Send Outlook Email.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Send Outlook Email.
What does the Send Outlook Email action do in Microsoft Outlook?
Sends a new email from the connected mailbox. For "external event → send personalised email from my account" workflows.
What inputs does Send Outlook Email require?
Required: To, Subject, Body (HTML). 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 Send Outlook Email support batch operations?
Yes. Run Send 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
Other Microsoft Outlook actions.
Action
Create Outlook Draft
Creates an email in the Drafts folder without sending. For "AI-generated reply suggestion → save as draft for user review" workflows.
ActionDelete Outlook Message
Soft-deletes a message (moves to Deleted Items). For "auto-archive newsletters after reading" or "delete known spam patterns" inbox-management workflows.
ActionGet Outlook Message
Returns a specific email with full body, attachments, headers. The standard lookup for "fetch this email captured upstream and process" workflows.
ActionList Outlook Mail Folders
Returns the folder structure of the mailbox (Inbox, Sent, custom folders). Useful for resolving folder IDs at workflow setup.
ActionList Outlook Messages
Paginated emails in a folder with filters. For "process unread emails matching pattern" batch workflows.
ActionMove Outlook Message
Moves a message to a different folder. For "auto-file by sender or content classification" inbox-organisation workflows.
Send send outlook email from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.