The NewMail event returns a parameter - Mail. This is the actual email. Extract a proxy from the event and that proxy will have all the properties of the email including SenderName, SenderEmailAddress and the Attachments. Decide if you are processing the email using those properties. The Attachments property is a collection. Send it to a ListLoop where you can extract a proxy - this is the attachment itself. Using the SaveAsFile method of the attachment proxy you can save it. Here is an example.
I have a requirement Where in Automation Based on NewMail Event, As Soon as the New Mail arrived in Outlook Inbox While Performing further actions,But the problem here is the automation is getting failed & stopped in below cases
In middle of doing current process(further automation Steps) if any Other New Mail Comes,
It is breaking the process (which has built as per the requirement to perform once New Email is received ) & starting the automation from beginning from NewMail Event(of outlook connector) is triggered.
So Please kindly provide a solution for this issue where in even any mail occurs in middle of performing the process (as per the requirement) The Automation should not break & complete the further process & then only it has to work on another New mail Even which arrives in Inbox in middle of the process.
You must specify a full path for the SaveAs command. In the automation above you can see that the step before the SaveAs was to concatenate C:\Temp\ to the name of the attachment. So in this example the attachments are being saved to C:\Temp.