Triggers, actions and your first scenario.

You've done the AI for leaders course, you get the idea, and now you want to actually build something. Good. This is the hands-on sequel, and by the end of it you'll have two or three real automations running. We'll keep it no-code the whole way. The first thing to get straight is how these tools think, because once the mental model clicks, the building is mostly wiring.

The whole idea in one sentence

An automation is just this: when something happens, do these things in order. The "when" is a trigger. The "do these things" are actions. That's the entire shape, whether you're using Make, Zapier or anything like them. A new enquiry lands on your website (trigger), so the tool adds the person to your CRM, sends them a quick acknowledgement, and drops a row in a spreadsheet (three actions). String a trigger and a few actions together and you've got what these tools call a scenario in Make, or a Zap in Zapier. Same thing, different name.

We'll teach mainly with Make, because its visual canvas makes the flow easy to see, and we'll point out where Zapier does the same job a little differently. Both have free or low-cost plans that are plenty to learn on. Pick one and stick with it for the course. The same trigger-and-action thinking carries straight over to a tool like n8n later, as our n8n workflow automation guide shows.

Triggers: the "when"

A trigger is the event that kicks everything off. Most are one of two kinds. An instant trigger fires the moment something happens, like a form being submitted or an email arriving. A scheduled trigger runs on a clock, say every morning at 8am or once a week, which is how a weekly digest gets built. You choose one trigger per scenario, and it's the thing that decides when the rest runs. Common ones you'll reach for: a new form submission, a new email in Gmail, a new row in a Google Sheet, or a new lead in a CRM.

Actions: the "do these things"

Actions are the steps that run, in order, after the trigger fires. Each one is a single job in one of your apps: create a CRM contact, send an email, append a sheet row, post a Slack message. The order matters, because each step can use data produced by the steps before it. That passing-along of data is the part that feels like magic the first time and obvious forever after, so let's name it properly.

Data flows down the chain

When the trigger fires, it hands the scenario a bundle of data. A form submission brings the name, the email, the message, the time. Every action below can reach into that bundle and use any field it needs. So your "send acknowledgement" step pulls the email address from the form. Your "create contact" step pulls the name and email. Your "add a row" step writes all of it to a sheet. You're not retyping anything: you're pointing each step at the right piece of data from above. The tools call this mapping, and it's the one skill that unlocks everything else. We give it the whole of the next lesson.

One more idea worth meeting now, because it tidies a lot of flows: a filter. A filter is a gate partway down the chain that says "only carry on if this is true." Only continue if the enquiry mentions a quote. Only send the alert if the deal is worth over $2,000. Filters keep an automation from doing the wrong thing on the wrong record.

Sketch it before you build it

Here's the habit that saves the most time, and it costs nothing. Before you open the tool, write the flow as one plain sentence. "When a new enquiry comes in through the contact form, add the person to the CRM, send them an acknowledgement, and add a row to the leads sheet." That sentence is your blueprint. It names the trigger, lists the actions in order, and quietly tells you which apps you'll need to connect. Get it clear on paper and the build becomes a matter of dragging the steps in and pointing the data where it goes. Try to design as you click and you'll build the wrong thing twice.

That's the model. A trigger fires, actions run in order, data flows down the chain, and a filter gates it where needed. Hold that and the rest of this course is just doing it with your own apps, and then making it clever and reliable. Next up: connecting your real apps and getting the data to land where it should.