Open app

DocumentationWorkflowsTriggers

Outlook · New email node

Kicks off the workflow as soon as a new email arrives in the inbox. The workflow waits a short grace period (10 s) before it fires, so you can still delete an accidentally sent email before automation kicks in. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

7 min readUpdated

What this node does

Kicks off the workflow as soon as a new email arrives in the inbox. The workflow waits a short grace period (10 s) before it fires, so you can still delete an accidentally sent email before automation kicks in.

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

  • Starts a new workflow run.
  • 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 · New email 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

Outlook · New email has one focused purpose. Its available settings appear when you select the node.

Settings

FieldMeaningArea
FolderChoices: Inbox, Junk, ArchiveStandard
Only from (optional)Only trigger on emails from this address.Standard
Subject contains (optional)Configure this value in the node panel.Standard
Check interval (seconds)How often Anymize checks for new emails.Standard

Inputs and outputs

InputMeaningType
StandardThis trigger does not require an input.JSON
OutputMeaningType
Email IDGraph message ID of the new email.text
SubjectConfigure this value in the node panel.text
SenderConfigure this value in the node panel.text
PreviewConfigure this value in the node panel.text
BodyThe message text (plain or HTML, depending on the filter).text
Received atConfigure this value in the node panel.text
Attachments?Configure this value in the node panel.boolean

Example and test run

Example inbox event: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "id": "AQMkADAwATMzAAMAMQ",
  "subject": "Neue Rechnung",
  "from": "billing@example.com",
  "bodyPreview": "Anbei die Rechnung für Oktober …",
  "body": "Hallo,\n\nanbei die Rechnung für Oktober …",
  "receivedAt": "2026-04-18T09:00:00Z",
  "hasAttachments": true
}

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.
  • Workflow does not start: activate it and check the trigger's test and production mode.

Related articles