I saw a community post/tutorial showing an IMAP node with the operation “moveEmail” (labelled something like “IMAP – moveEmail: email”).
I’m using n8n Cloud, and I can’t find any IMAP node/action that supports MOVE (I only see the Email Trigger (IMAP) with actions like “Mark as Read” / “Nothing”, and no separate “IMAP” node with move/copy/delete).
Could someone point me to:
1. Where exactly this “IMAP moveEmail” node comes from (core node vs. community node)?
2. The node name/package if it’s a community node, and whether it’s available on n8n Cloud (or only self-hosted)?
3. Any recommended alternative approach on n8n Cloud if MOVE isn’t supported?
Hey! Which email client are you working with? And what do you mean by “move”? Do you mean applying a label in gmail? Or forwarding the email to a new address?
If so, you’re limited to verified community nodes on n8n cloud. This doesn’t appear to be one of them, unfortunately. If you have “verified community nodes” enabled in n8n cloud but do not see this one as being available, then you can’t use it from n8n cloud.
Hi @Ralph, Please can you share the community post / tutorial so we can see which node was referenced. Please be aware that some older posts and tutrials found on the internet might be referencing older version of n8n where some nodes have changed, causing confusion on where to find them
The screenshot shows a node labelled “IMAP – moveEmail: email”.
I’m on n8n Cloud and can only see Email Trigger (IMAP) (Mark as Read / Nothing).
We want to use IMAP moveEmail to move the processed message out of the INBOX into a subfolder (e.g., “Done” / “Erledigt”) after the workflow finishes, so the inbox stays clean and the email is marked as completed/archived.
I’m using n8n Cloud with a Strato IMAP mailbox (classic IMAP server + folders, not Gmail).
By “move” I mean a real IMAP MOVE operation: after my workflow processes the incoming email (extract PDF, upload to Google Drive, send notification), I want to move the original message from INBOX to an IMAP subfolder, e.g. INBOX/Erledigt (Done/Processed), so it’s out of the inbox.
So: no Gmail labels, and not forwarding—just moving the email into a folder on the IMAP server.
thank you for your reply and the hint about the community IMAP node. That already helped a lot.
Just to clarify my goal/setup: I’m using n8n Cloud with a Strato IMAP mailbox. The workflow processes incoming emails with PDF attachments (save the PDF to Google Drive, send a notification email), and then I want to move the original email from INBOX to a subfolder like “Erledigt/Done” to keep the inbox clean.
Since I can’t find any official n8n core node/action that supports IMAP MOVE (only “Mark as Read” / “Nothing” in the IMAP Email Trigger), I’m wondering:
Do you know any official / core-node way to achieve this on n8n Cloud (e.g., another email node, different approach, or recommended workaround)?
If not, what would you consider the best practice on n8n Cloud for this “INBOX → Done folder” use case?
Hi @Ralph, That looks like some community node which we wont be able to support here. On cloud you’ll also only be able to install officially approved community nodes which I dont see that one on the list
thanks a lot for the clarification — I really appreciate it.
My goal is simple: after my workflow processed the incoming email (and uploaded the PDF), I want to move the original email from INBOX to a subfolder (e.g. “Done/Processed”) so the inbox stays clean.
Since the community IMAP node isn’t available on n8n Cloud: is there any recommended workaround using only official n8n nodes on Cloud (for example via another email node, forwarding, labels/folders, or any best-practice pattern)?
There’s no official node for the IMAP functionality you’re looking for beyond the IMAP trigger node. I’ve accessed IMAP servers programmatically with Python using the imaplib library. It’s something you could do as well. Unfortunately, the python code node would not be able to import in the lib with n8n cloud (due to security restrictions). If you’re comfortable, you can easily create an AWS lambda or Azure function. Create a HTTP request node, and ust toss over the “message-id” and a target folder. That’s how I would design this.
The code would be something like:
0) find email by Message-ID (unique identifier for emails)
copy email found to target folder
delete from inbox
Test the code in isolation thoroughly before integrating into your workflow.
Das suche ich auch bereits verzweifelt, aber das IMAP Node scheint NUR “als gelesen markieren” zu können. Ich kenne es auch von anderen Tools (paperless etc.) eine Mail einfach zu verarbeiten wenn es im OrdnerXY ist und dann in OrdnerArchiv bewegen. Scheint nicht abbildbar zu sein hiermit leider.