In some cases, one action will gather data to be used for future actions. For example, if we tried to send our emails before they were created, the workflow wouldn't make sense, and we would get errors.

This is important to keep in mind as you build your workflows because if you have actions in the wrong order, you may get some pretty funky results. When it's done processing action #2, it will move on to action #3, and so on.

When it's done processing action #1, it will move on to action #2. When you run your workflow, it will always begin with action #1.

Gather a list of people (using Address Book) who will be celebrating a birthday todayīefore we continue, let me interject a concept here that you will need to understand when using Automator (it may seem obvious to some, but maybe not all).In this example, there will be three actions: With our blank canvas open, we'll need to drag various actions onto the canvas to build our workflow. To do this, we need to create a new ' Workflow' document. In this example, we're going to create a workflow that sends an email to anyone in our Address Book who has a birthday today. I will also show you how to convert that workflow to a calendar item, which will allow us to schedule it to run automatically. In this post, I will take things a little deeper and walk you through creating your first multi-action workflow, explaining how each action feeds into the next. It was a simple workflow, but hopefully it gave you a good idea of how to begin using Automator to automate your very own workflows. In yesterday's Automator blog post ( Automator: Understanding the UI and Creating Your First Workflow), I walked you through how to create your very first workflow using Automator.

Automator mac sending recuring emails