When to automate

code • March 27, 2019

You will know if you have a candidate for an automation when you have: a frequent manual process, consistent data, and a trigger.

1. Frequent manual process

The frequent part in frequent manual process is whatever allows you to get the job done. Here are a few examples of some manual processes you may see in your day to day:

2. Consistent data

Having a consistent data source can make or break your ability to automate. Check to see that your data:

3. A trigger

Your automation needs a trigger to know when to run. Your automation could run on a schedule:

Or your automation can run in response to another event. For example, if you send a tweet with a hashtag, then you could trigger an automation to save the contents of that tweet to a spreadsheet.

Should I build it custom?

Before creating something from scratch, check to see if a service exists that can do it for you. Services like Zapier, IFTTT, and Apple’s Shortcuts can make automation as straight forward as connecting your accounts and clicking a few buttons. Slack also offers built-in features and apps to help automate processes.

If services cannot connect in the way you need or if you have privacy concerns, then you’ll need to create a custom automation.

Where can I host a custom automation?

You have a lot of options to host your code and schedule it or listen for changes. Here are a couple that I’ve worked with:

Is my automation helpful?

You should regularly check-in with your automation to make sure it still accomplishes your goal, especially in the company of others.

What’s next?

Finally, have a work-in-progress mindset with your automation. Your workflows and productivity constantly change, so should your automation. Ask for colleagues for feedback and see how others interact with your automation, and then iterate.

Keep reading code