Your first workflow, from a ready-made template

▸MODULE 2 / YOUR FIRST WORKFLOW

What we are talking about

You have already sorted out which tasks are worth automating at all. Now you build something that actually runs for the first time. And I want to take the fear out of this right from the start: you do not begin with a blank canvas. You load a ready-made template, look it over, and run it once. That is all this lesson asks of you.

That is deliberate. The hardest moment in automation is not the building itself, it is staring at an empty surface and not knowing where to start. We skip that moment entirely. By the end of this lesson you will have started a simple workflow, watched it run once, and understood the three parts it is made of. That is exactly the foundation you need; everything that follows builds on it.

The simplest flow, traced by hand

Every workflow, meaning every chain of automatic steps that run one after another, follows the same core pattern at its heart. Before you click anything, let us trace that pattern slowly by hand, using a picture from your everyday life.

Imagine someone signs up for your newsletter through a form on your website. The moment that entry arrives, what normally happens at your desk is this: you take the name and email address, you add the person to your contact list, and you send them a short welcome email. One nudge, then two actions, then a visible result.

That is exactly how a workflow is built. It has a starting point that sets things in motion, and then a series of steps it works through one by one. In plain words, without any technical language: a trigger, then an action, then an action. Your first workflow does not need any more pieces than that.

The trigger: the nudge that starts everything

The first technical term, explained in half a sentence: the trigger is the event that starts the workflow. As long as the trigger has not fired, nothing happens. The workflow simply waits.

In our example, the trigger is the new entry in the form. Only when someone signs up does the workflow wake up and get going. You can think of the trigger as a doorbell: it hangs on the wall all day doing nothing, and the moment someone presses it, something is set in motion. No ring, no motion.

One thing for your peace of mind: a workflow has exactly one trigger at the start. There are not two doorbells. There is one clear occasion, and the chain responds to that.

The step: one node, one action

The second technical term: in the tool you will be using, each individual building block of the chain is called a node, meaning simply a step, a single box that does one thing. Some tools call it a step, others call it a node. The meaning is the same.

Staying with the picture: after the doorbell rings, meaning after the trigger fires, the actions follow one by one. The first step adds the contact. The second step sends the welcome email. On screen you see this as a row of boxes connected from left to right by a line, like beads on a string. The trigger is the first box; each further step is its own box after it.

The only thing you need to hold in your head is this picture: one trigger on the left, then steps going right. Once you can see that, you have understood the structure of every workflow you will ever encounter.

Why we start with a template and not a blank canvas

Now the third term, and the real trick of this lesson: a template is a workflow that has already been set up and that you import with a single click and then adjust to your own needs. You do not have to line up the boxes from scratch. They are already there, already connected, already arranged sensibly.

Think of the difference in cooking terms. Starting from a blank canvas is like standing in an empty kitchen and having to invent the recipe yourself. Loading a template is like taking a tried-and-tested recipe from a cookbook: the steps are already in the right order, and you simply swap in your own ingredients. Both paths lead to a meal. One of them is considerably calmer for a first attempt.

Before you click: your workflow in words

One calm step before you touch a template. It helps enormously to write out your planned workflow in a single sentence first, in the form: trigger, then action, then action. Anyone who cannot put it into words will get stuck clicking later. Anyone who can say it in one sentence will find the right template in the overview much more easily.

The practice prompt below helps you do exactly that. You describe a small, straightforward task from your everyday life, and the AI tool you are working with helps you break it cleanly into the three parts. Copy it and use it before you go looking for a template in your automation tool.

I am planning my very first, simple automation workflow and want to
break it down in words before I click anything anywhere.

Here is the small task it should handle for me, in one sentence:
[Describe it, for example: "When someone fills in my form, the contact
should be saved and a short welcome email sent."]

Help me break that down into exactly these three parts, and ask me the
questions one at a time, each one after my answer:
1. The trigger: which single event should start the workflow?
2. The first action: what should happen first, as soon as the trigger fires?
3. The second action: what should happen after that, as the visible result?

Make sure there is exactly one trigger and keep the actions simple.
Summarize the result at the end in a single sentence of the form
"trigger, then action, then action", in plain words, without technical language.

Once you have that one sentence, the actual searching and launching of the template is surprisingly quick: you go to the template library in your tool, look for the pattern that matches your sentence, import the template, and run it once as a test. You will see how the trigger sets the chain in motion and the steps run through one after another.

The honest assessment

This lesson deliberately teaches you only the simplest possible flow: one trigger, then one action, then one action, started from a ready-made template. It does not yet make you a workflow builder, and that is exactly right. The first run will often be rough; maybe there is a placeholder name in the email instead of the real one, and that is not a mistake, it is the next step.

What this lesson does not cover: it does not yet touch the data fields, meaning the question of how the real name from the form travels to the right place in the email. And it does not yet introduce conditions, meaning no "if this, then something different". Both have their own place later in this module, fields first, then conditions. We will work through them calmly, one at a time.

One question often comes up early on and fairly so: where does this workflow actually run, and what does it cost? That is exactly what the next lesson covers. There we look at where your workflow can run without any infrastructure of your own, and we talk honestly about the costs before you commit.