Automating Email Processing Part 2

I covered automation in processing email before it gets to your inbox.

I covered two main assumptions that might not apply to every circumstance. The first assumption is that your email service itself has sophisticated enough rules systems in place that you can use. The other belief is the primary services or tools you want to send an email out to have their email addresses, so they are forwarded.

If one of these assumptions is a fault or both, does that mean you can’t automate your email?

No, this is where using third party automation services comes in. I’m staying away from the device or local automation, for now, to make this all as cloud and server-based as possible. The reason for this is to make sure the automation happens whatever your local circumstances are (no power or signal etc.). This means there is a minimal email you have to deal with on your devices.

The most popular automation services are IFTTT and Zapier.

Your choice between them or other services may depend on the platforms and services you are trying to connect to. Also, you don’t need to limit yourself to one automation service depending on circumstance or even take advantage of each to create a chain of automation services.

If you’re looking for more sophisticated rules you need to create, then Zapier may be your answer. There’s a lot more flexibility there for multiple branches and steps and filtering text in different ways, and even adding your programming scripts if need be.

One caveat with the third party services is there is a finite time when email arrives and is often the trigger to the automation, meaning you could see email on your device before it’s been processed. But trust your system.

This post was created with Typeshare