Move Email
Infoveave Data Automation — Email
Process the email. Move it. Keep your inbox clean — automatically.
Every automated email processing workflow has the same challenge: once an email has been processed, how do you prevent it from being processed again? Move Email solves this by routing processed messages to designated folders based on their workflow outcome. Approved invoices go to 'Archived'. Escalated support tickets go to 'Priority Inbox'. Processing failures go to 'Review Queue'. The folder routing is driven by a configurable status-to-folder mapping table — making Move Email a clean, auditable way to maintain inbox hygiene as part of every automated email pipeline.
What Move Email does
Move emails between folders in a connected IMAP mailbox based on configurable status-to-folder mapping rules inside your Infoveave workflow. Automatically archive, triage, and organize processed emails without manual inbox management.
When to use Move Email
- You want to archive or remove processed emails from the inbox after Download Email or Receive Email has extracted their content
- You need to route emails to different destination folders based on the processing outcome — approved, rejected, escalated, pending
- You are running a support ticket or approval workflow where email triage is part of the process
- You want to ensure each email is processed exactly once by moving it out of the monitored folder after processing
When to avoid it
- You need to download or read emails — use Download Email or the Gmail/Outlook receive activity
- You need to send a new email — use Send Email
- Your mail server does not support IMAP folder operations — verify IMAP folder move support with your mail provider
Where it fits in your Infoveave automation
Move Email is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Move Email
Real scenarios where this transformation saves hours of manual work.
Support Request Email Triage
A support workflow downloads unread emails from the support inbox, classifies each request by urgency using a transformation activity, and uses Move Email with a Status-to-Folder map to route 'Approved' tickets to 'Resolved Tickets', 'Escalated' tickets to 'Priority Inbox', and 'Pending' tickets to 'Review Queue'. The inbox is kept clear with each workflow run.
Invoice Processing Archive
An AP automation workflow downloads supplier invoices from the inbox, extracts and validates data, and loads confirmed records into the accounting system. Move Email archives successfully processed invoices to 'Processed Invoices' and moves failed or unrecognized formats to 'Manual Review'. Both folders are auditable for compliance.
Leave Request Email Processing
A leave management workflow reads approval decision emails from a shared HR mailbox and updates the HR system. Move Email routes emails with 'Approved' status to 'Approved Requests' and 'Rejected' status to 'Rejected Requests', maintaining a clean organized archive of all processed requests.
See Move Email in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
imap-office365email_uidStatus = Approved → Archived | Status = Escalated → Priority Inbox | Status = Pending → Review QueueInput Data
| email_uid | Status |
|---|---|
| 8722 | Approved |
| 8723 | Escalated |
| 8724 | Pending |
Output Data
| UID | Status | Destination Folder | Result |
|---|---|---|---|
| 8722 | Approved | Archived | Moved |
| 8723 | Escalated | Priority Inbox | Moved |
| 8724 | Pending | Review Queue | Moved |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Connection
The registered IMAP email server connection. Configured in Infoveave Studio with server URL, port, and credentials. Must support IMAP folder move operations.
Message Identifier Column
The column in the input data that contains the unique email UID or message ID from the mail server. This ID is used to locate the exact email on the server. The ID is typically produced by a prior Download Email activity in the same workflow.
Configuration Map
A rule table that maps input column values to destination folders. Each row specifies a column to check (e.g., 'Status'), a value to match (e.g., 'Approved'), and the destination folder if the condition is met (e.g., 'Archived'). Multiple rules can be defined, and the first matching rule determines the destination.
Frequently asked questions
Everything you need to know about Move Email in Infoveave.
Also in Email — and what runs before & after
Transformations in the same family as Move Email, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Move Email is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
