Short answer: Drop the "Microsoft Outlook → Send Outlook Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"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}}"}
{"id": "msg_mic_123","status": "sent","success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.