Email Mover (Labs) Node

I have a reporting process that requires ingesting either links to download from the platform, or attachments. I move each corresponding data source’s email to its own folder in the email (which uses POP/IMAP). Some of the emails are a straight attachment that gets saved to it’s own folder, and others have regex to parse out the download URL link and pass through as URL to download and move them to their own folder (image below is example):


Everything is working as intended, except that the email mover node isn’t moving the email from it’s original location to another location (as noted, each folder is named after it’s specific data source, and I want to move them to the folder ZZProcessed so that the individual email folder remain either empty, or have one email when the report is sent.

I have the original folder set up as ‘source’, the Email ID passes through, and the Target folder is the ZZProcessed I want it to go into (to save all historical emails).

The node reflects no error:


But the emails aren’t moving from Source to Target. Is there something I am missing, or a flag I have to activate in my email supplier? The credentials are accurate since the data is being read.

Any help would be appreciated.

Hi @ebarr, we’re very sorry that you experienced this issue with the Email Mover (Labs) node. Did you find a solution to it yet? If not, two questions:

  • Do you have write permission over the folder you’re trying to move the email to?
  • Do you always get this error when using this node or does it happen only for a few instances? If the latter is correct, could you give us a few examples of instances you get this error for?

Thanks!

2 Likes

Yes, it’s my email instance. I created a rule that moves emails into different folders in my inbox (subfolders of inbox) so that I can download attachments from each email source, then move each email to a ‘processed data’ folder in the email. some emails appear to move, while others remain behind. I have four reports from Amazon, as an example, two get moved, two do not, and that’s the same source. I use one login branched to the different folders, I tried including a ‘wait’ node thinking maybe they are stepping on each other, but that didn’t seem to work.

Hello @ebarr ,
can you tell us which email provider you are using? This might help us to replicate the problem and find the error. In addition could you use flow variable connections to make sure that each email mover node is processed after the other. Maybe it is a concurrency problem.
Thanks
Tobias

2 Likes

It looks like it is working. It would move when running one file test, but only a couple would move when running for multiple report attachments. I tried with using the ‘wait’ node in between each adding an incremental :05 in between each mover and it seemed that perhaps 40-50% moved. I was using outlook, then changed to the ‘new’ outlook vs. classic and it seems that all files are now being moved. I don’t understand how an interface would change the behavior, so this may just be correlated, but the issue seems to have resolved itself. Great tool, though! very helpful and has saved a lot of nitpicky steps!

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.