Open app

DocumentationWorkflowsTriggers

Receive email (IMAP) node

Starts the workflow when a new email arrives in any mailbox that supports IMAP: your own mail server, a hosting package or a shared mailbox. Each trigger has its own mailbox. Anymize only reads along: it moves nothing and marks nothing as read. New emails are processed after a short grace period (10 s). Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

7 min readUpdated

What this node does

Starts the workflow when a new email arrives in any mailbox that supports IMAP: your own mail server, a hosting package or a shared mailbox. Each trigger has its own mailbox. Anymize only reads along: it moves nothing and marks nothing as read. New emails are processed after a short grace period (10 s).

Use Receive email (IMAP) 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 Receive email (IMAP) from the node catalog.
  2. 02Store the credentials in Workflow Secrets and select them in the "Mailbox" field.
  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

Receive email (IMAP) has one focused purpose. Its available settings appear when you select the node.

Settings

FieldMeaningArea
MailboxThe IMAP credentials of the mailbox to watch. You create them under workflow credentials. Only the name is stored in the workflow, never the password.Standard
FolderThe folder name as the mail server knows it, for example INBOX or INBOX/Invoices. Case matters.Standard
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 looks for new emails. At least 60 seconds.Standard

Inputs and outputs

InputMeaningType
StandardThis trigger does not require an input.JSON
OutputMeaningType
Email IDUID of the email in the folder, as text.text
UIDUID of the email in the folder. Unique together with the folder.number
Message IDMessage ID from the mail header.text
FolderConfigure this value in the node panel.text
SubjectConfigure this value in the node panel.text
SenderSender address.text
Sender nameConfigure this value in the node panel.text
RecipientsRecipient addresses, separated by commas.text
PreviewConfigure this value in the node panel.text
BodyThe readable message text. Attachments are not loaded.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": "1842",
  "uid": 1842,
  "messageId": "<20261029.101500.7@mail.example.com>",
  "folder": "INBOX",
  "subject": "Neue Rechnung",
  "from": "billing@example.com",
  "fromName": "Buchhaltung Muster GmbH",
  "to": "info@firma.de",
  "bodyPreview": "Anbei die Rechnung für Oktober …",
  "body": "Hallo,\n\nanbei die Rechnung für Oktober …",
  "receivedAt": "2026-10-29T09:00:00Z",
  "hasAttachments": true
}

Access and security

The credentials live in a Workflow Secret that you select in the "Mailbox" field. The workflow only holds the secret's name, never the key itself.

Keys and credentials belong in Workflow Secrets or your connected accounts. Never paste them as plain text into 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.
  • Workflow does not start: activate it and check the trigger's test and production mode.

Related articles