Email Parser

Extract data from incoming emails and automate your workflow

MENUMENU
DOCUMENTATION TOPICSDOCUMENTATION TOPICS

Run conditions and action chaining

 

The idea behind Email Parser, as shown in the How it works help topic, is to build on the left panel a set of items that step-by-step process the incoming email the way you want.

Email sources and email parsers are connected using simple rules. Email parsers just take the email from an email source or an email filter when an email is available, it is that simple and the program does not ask for more details. But for action this connection is a bit more complex and therefore versatile. This help topic covers all the possible “run conditions” you can use:

 

 

 

 

 

when_an_email_is_available_from
“Action-1” is run whenever a new email is found in the mailbox

When unprocessed email is available at …

The process is run directly after the email is received. Any email parsers will be bypassed.The only fields that the process will have available are those that come by default with any email: From, To, Subject, etc.The process will be run once for every incoming email or, in the case you choose an email filter, once for every email that has passed the filter. You can also set the process to be run for the emails that have not passed the filter.


when_an_email_and_parsed_fields_are_available_from
“Capture data” is run once for every received email. After each run of “Capture data” the “Save to Excel” is also run with the resulting fields

When parsed fields are available at …

The process is run after the connected email parser captures the fields. This is the most common run condition for the first process in the chain.Apart from the default header fields that come by default with any email (From, To, Subject…) the process will have the fields captured from the email parser.The process will be run once for every email that the email parser processes.


after_this_automated_process_succesfully_runs
Once “Capture data” is run for a given email, “database update” is run with the captured fields. Finally “Save to Excel” is also run. The process is repeated for every email

After this action

The process is run after the other action is run. It will be run each time the previous process runs.


after_this_automated_process_succesfully_runs
Once “Capture data” is run for a given email, “database update” is run with the captured fields. Finally “Save to Excel” is also run but only if the database operation was successful. The process is repeated for every email

After this action is successfully run

The action is run only if the previous one is successfully run. It will be run each time the previous process successfully runs.


after_this_automated_process_fails
In the case “database update” fails the “Send email reporting error to the admin” is run. If “database update” successfully runs it is not run.

After this action fails

The action will run only if the previous one does not run successfully.This is very useful to, for example, handle unexpected errors. Note that the arrow in this case is slightly brighter. It will be run each time the previous process fails.


when_called_by_this_script__process
Scripts like “do some complex stuff” can call any other processes connected to them this way.

When called by this script

Script actions are a special kind of processes that can call other processes. The called processes must be have the run condition set to this value.


before_and_after_any_emails_are_processed
“Run external PREprocess” will be run just after clicking “Run” on the toolbar. Once all the emails are processed “Run external POSTprocess” will be run

Before any email is processed

The process will be run only once regardless the number of emails received and will be launched before any other process.


After all the emails are processed

The process will be run only once regardless the number of emails received and will be launched after the rest of processes are run.