DocumentationWorkflowsApps and services

Outlook node

Mail operations (send, list, reply, move) on your connected Outlook account. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

11 min readUpdated

What this node does

Mail operations (send, list, reply, move) on your connected Outlook account.

Use Outlook as a clearly defined step in an anymize workflow.

  • Processes one input.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Outlook from the node catalog.
  2. 02Select your microsoft connection. You can create it directly in the workflow if needed.
  3. 03Complete the required fields and map values from previous steps.
  4. 04Run the node with a small test record and inspect its output.
  5. 05Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Choose the required function in Action. The panel then shows the relevant settings.

  • Send email
  • List emails
  • Reply to email
  • Move email

Settings

FieldMeaningArea
Import formatConfigure this value in the node panel.Standard
Microsoft accountChoose the connected account for this step.Standard
Reply addressConfigure this value in the node panel.Standard
CategoriesConfigure this value in the node panel.Standard
ImportanceChoices: Low, Normal, HighStandard
Request read receiptConfigure this value in the node panel.Standard
Additional message fieldsPreserves the additional message headers in your template.Standard
ResultChoices: Overview, All available fields, Choose fieldsStandard
Result fieldsThese Outlook fields are included for each match.Standard
Fetch all matchesFetches additional result pages. Very large results stop with a clear error.Standard
Narrow down messagesChoices: All messages, Search term, Template filtersStandard
Message filtersPreserves the selected criteria from your template. Unset criteria stay unrestricted.Standard
ActionChoices: Send email, List emails, Reply to email, Move emailStandard
ToConfigure this value in the node panel.Standard
SubjectConfigure this value in the node panel.Standard
ContentConfigure this value in the node panel.Standard
FormatSend as plain text or as formatted HTML.Standard
CCConfigure this value in the node panel.Standard
BCCConfigure this value in the node panel.Standard
Save to SentConfigure this value in the node panel.Standard
FolderChoices: Inbox, Sent, Drafts, Junk, ArchiveStandard
Count (max. 50)Configure this value in the node panel.Standard
Search termFilters the mails. Plain text is enough; for pros, things like from:"boss@company.com" or subject:invoice work too.Standard
Only unreadConfigure this value in the node panel.Standard
Which email?The ID of the original mail. Drag it in here from an upstream step (e.g. "List emails" or the mail trigger).Standard
Reply to allConfigure this value in the node panel.Standard
Destination folderChoices: Junk, Archive, Deleted items, Inbox, Custom folder ID …Standard
Folder IDThe Graph folder ID (e.g. from GET /me/mailFolders).Standard
Run once per itemOff (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry.Standard
If one item fails"Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file.Standard
Pause between items (milliseconds)Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes).Standard

Inputs and outputs

InputMeaningType
StandardReceives the complete result from the previous step.JSON
OutputMeaningType
StandardMakes the result available to the next step as JSON.JSON

This node can process lists item by item. Error handling and the delay between items are available in advanced settings.

Example and test run

Quick test mail: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "to": "max@example.com",
  "subject": "Hallo aus dem Workflow",
  "body": "Das ist ein automatischer Test."
}

Access and security

This node uses a connected microsoft account. Review the requested permissions and grant only the required access.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • Connection rejected: reconnect the service and grant the permissions required by this step.
  • List processed once: enable per-item execution in advanced settings.