I am making a scenario for my client whose is using his mail server Through IMAP and mailbox connected with computer installed outlook app.
My objective is to receive all his emails and based on criteria move them to separate folders .
I was able to download the “Communityapp” via npm for this work but to my surprise my scenario is working fine but the email is not moving into the expected folder .
Hi @areeb Welcome!
I guess this happens due to the invalid path of the folder but if it is correct , you should validate that the folder have all the permissions to perform the action, hope this helps.
When using IMAP with n8n, it’s common for workflows to appear to run successfully while emails are not actually moved on the server. This usually happens because IMAP operations are very strict about identifiers and folder paths, and the node may fail silently if something is slightly misconfigured.
Recommended solution: Store processed emails
Store the email UID externally (for example in the n8n Data Store or a database) and, before moving the email, check if that UID was already processed; if it was, skip it, and if not, move the email and persist the UID to prevent reprocessing.
Alternative solution
Ensure the correct IMAP UID is used
Make sure the Move Email node receives the numeric attributes.uid from the IMAP trigger and not a stringified or incorrectly referenced value.
Verify the exact target folder path
Confirm that the destination folder already exists on the IMAP server and that its name and hierarchy exactly match what is configured in the node.
Validate IMAP behavior independently of Outlook
Remember that the email move happens on the IMAP server and Outlook only reflects the server state after synchronization.