Move email
Description
Moves a message to another folder on the same server. Takes an email object from Find/Get email — the server connection comes from the email itself. The message has no output because its UID in the destination folder is not reliably knowable; look it up with Find emails if you need it. Branches on success/error.
When to use
Use Move email to file a message once you have finished with it — into an archive folder, a per-customer folder, or a “needs review” folder a human watches. Moving is the usual companion to Set email flag in a polling pipeline: flag it read so the search stops matching it, move it so the inbox stays clean.
The node has no data output, deliberately. After a move, the message has a new UID in the destination folder, and that UID is only reliably reported by servers implementing the UIDPLUS extension. Returning an email object that is sometimes wrong would be worse than returning nothing, so if you need the moved message again, look it up with Find emails against the destination folder.
The destination must already exist; a move into a missing folder takes the Error branch. Run Create email folder first when the destination is derived at runtime — it succeeds whether or not the folder is already there.
The move happens within one server. There is no cross-account move; copy the content into a new message if you need that.
Pins
Input pins
| Pin | Type | Default | Notes |
|---|---|---|---|
| — | An email object from Find emails or Get email. The source folder and the server connection both come from the email itself, so this node needs no credentials. | ||
| To folder | string | — | Full path of the destination folder on the same server, using the server's hierarchy separator. Must not be blank, and must already exist — pair with Create email folder if it might not. |
Execution pins
| Pin | Direction |
|---|---|
| In | Input |
| Success | Output |
| Error | Output |
Example
Keep an order inbox tidy. Inside the per-message loop after Find emails and
Read email, once processing has succeeded, wire the loop element into Set
email flag (SEEN, true), then into Move email with To folder
INBOX/Processed. Wire the Error pin of both into a Log message node so a
server-side failure is visible without aborting the rest of the batch.