Actions12
- Mailbox Actions
- Email Actions
Overview
This node connects to an IMAP email server to perform various email-related operations. Specifically, the Move Email operation allows users to move one or multiple emails from a source mailbox folder to a destination mailbox folder on the IMAP server.
Common scenarios where this node is useful include:
- Organizing incoming emails by automatically moving them to specific folders based on certain criteria.
- Archiving emails by moving them from the inbox to archive folders.
- Automating email workflows that require relocating messages between mailboxes.
For example, you could use this node to move all emails with a particular subject line from the "INBOX" to a "Processed" folder after they have been handled by another workflow step.
Properties
| Name | Meaning |
|---|---|
| Credential Type | Choose which credentials to use for connecting to the IMAP server: - IMAP (credentials from this node) - N8N IMAP Trigger Node (reuse existing credentials from an IMAP trigger node) |
| Source Mailbox | The mailbox folder from which the email(s) will be moved. Can be selected from a list of mailboxes or specified by full path. Required. |
| Email UID | The unique identifier(s) of the email(s) to move. Supports comma-separated lists to move multiple emails at once. |
| Destination Mailbox | The mailbox folder to which the email(s) will be moved. Can be selected from a list of mailboxes or specified by full path. Required. |
Output
The node outputs JSON data representing the result of the move operation. This typically includes information about the emails that were successfully moved. The exact structure depends on the underlying IMAP library's response but generally confirms the UIDs of moved emails and any status messages.
The node does not output binary data.
Dependencies
- Requires valid IMAP credentials to connect to the email server. These can be provided directly in the node or reused from an existing IMAP trigger node.
- The node uses an IMAP client library internally to communicate with the email server.
- No additional external services are required beyond the IMAP server itself.
- Environment variable
N8N_LOG_LEVELcan influence logging verbosity (e.g., setting it to "debug" enables detailed logs).
Troubleshooting
- Connection failures: Errors during connection usually indicate incorrect credentials, wrong server address, or network issues. Verify the IMAP credentials and server accessibility.
- Invalid mailbox names: If the source or destination mailbox does not exist or is misspelled, the operation will fail. Use the mailbox list selector to avoid typos.
- Email UID errors: Providing invalid or non-existent email UIDs will cause the move operation to fail. Ensure the UIDs correspond to actual emails in the source mailbox.
- Permission issues: Some IMAP servers restrict moving emails between certain folders. Check server permissions if moves fail unexpectedly.
- Error messages: The node surfaces error messages from the IMAP server or client library. Common messages include authentication failures, mailbox not found, or permission denied. Review these messages to adjust configuration accordingly.