What is the primary function of the IMAP node in n8n?
The IMAP node primarily acts as a trigger to start workflows whenever new emails arrive in a monitored mailbox, enabling crucial email-based Integrations.
How can the IMAP node be used beyond just starting a workflow?
While commonly used as a trigger, the IMAP node can also be configured to perform operations within a running workflow, such as fetching specific emails, marking them as read, or moving them between folders.
How does the IMAP trigger ensure it doesn't process the same email twice?
When configured as a trigger, the node maintains state by remembering the IDs or dates of the last processed messages, ensuring that the workflow is only activated by truly new messages.
What information does the IMAP node output when it runs?
When activated, the IMAP node typically outputs detailed message data, including headers, body content (plain text and HTML), sender information, and any attachments, which subsequent nodes can then process.
Can I use the IMAP node to monitor multiple email folders or accounts in one workflow?
Yes, while a single IMAP node trigger is usually configured for one folder (like INBOX) on one account, you can add multiple IMAP nodes within the same workflow or use separate workflows for different Integrations or accounts.