Workflow 31: How to Build Your First AI Automation, Step by Step

This is the last one.

Thirty workflows in, the question I get most is some version of: how do I build one of these myself, from nothing?

So this one walks through it, start to finish, using a single process as the example. By the end you'll have what you need to build your first real AI automation.

What this replaces

Opening an automation tool with no plan and trying to build from the canvas.

It fails for a predictable reason. You're designing the process and building the automation at the same time, which means you're making decisions in the tool that should have been made on paper.

Automation or AI automation?

These get confused constantly, and the difference decides what you're building.

An automation always does the same thing. A plus B equals C.

Here's one I've used: send the keyword "gimme" to my Instagram, and it sends back a handout I give out when I speak. Same trigger, same response, every time. Useful, but there's no thinking in it.

An AI automation has a step that thinks. Something like A plus B, multiplied by X, equals C.

Bibbidi, my content repurposing agent, is the example. Twice a week, when a new video goes live on Scale You on Thursday or my main channel on Sunday, he pulls the transcript, runs it through AI, and produces a different set of posts depending on what I actually said. Same trigger, different output every time, because there's something in the middle making decisions.

Most people who say they want AI automation actually want the first kind. That's fine, and it's simpler. Know which one you're building.

Blueprint

Brain dump the process as a human currently does it.

Take client onboarding as the example. The client pays. You see the payment notification. Someone creates a Notion page and customizes it. Someone alerts the right people that a job is starting. Someone pulls the sales call recording from the CRM. And so on.

Write all of it down, including the steps that feel too small to mention. Those are usually where the automation breaks later.

Organize

Now map where everything lives.

Which tool does each step use? Where does the information go? What filters or conditions apply? And one people forget: if your main tool goes down, where's the backup, and where does the data live then?

You're turning the brain dump into something another person could follow.

Systematize

Write the recipe.

Think of it as a recipe for the outcome, one you'd want to get the same way every time. It needs:

• The purpose. What this process is for and why it exists.
• What's needed. Tools, access, and anything you need to know before starting.
• The steps. In order, chronological, one action each. Send this email. Grab this template from here. Notify this person. Add screenshots or a recording if it helps.

This document is what the AI will build from, so the clearer it is, the better the automation.

How to set it up

1. Pick one process and write down every step a person currently does, including the small ones.
2. Map where each step's information lives, including where the backup goes if a tool fails.
3. Write the SOP: the purpose, what's needed, and every step in order.
4. Mark each step as tool to tool, which you automate, or seen by a person, which gets a human gate.
5. Give the SOP and your Me and Business files to Claude or ChatGPT, and ask it to build the workflow in n8n or Make.
6. Run it on real work, and fix what breaks.

Assign

Now go through every step and decide: automate it, delegate it, or a mix of both.

The filter is simple:

• If a person will see it or interact with it, put a human gate in front of it. A person reviews before it goes out.
• If it's tool to tool, automate it completely. Nobody needs to check a payment notification creating a Notion page.

In the onboarding example, creating the page, alerting the team, and pulling the recording can all run on their own. The welcome email the client reads gets a human gate. The onboarding call stays fully human.

Rule of thumb from this build: if a human sees it, a human checks it.

Integrate

Now you build.

Take your SOP to ChatGPT, Claude, or whatever you use, as long as it can connect to an automation platform like n8n or Make. Give it the document and ask for the workflow:

Here is the SOP for [PROCESS] in my business.

[PASTE YOUR SOP: purpose, what's needed, and every step in order]

Build this as an [n8n / Make] workflow that produces the same outcome
every time.

Steps that are tool to tool should run automatically. Steps where a person
will see or interact with the output need a human approval gate before
anything goes out. I've marked which is which in the SOP.

Tell me:
- Which tools and connections I'll need
- What each will cost, and which free tiers cover it
- Anything in the SOP that's ambiguous before you build

Ask me questions rather than assuming.

Give it context about you and your business as well. The Me file and the Business file from earlier in this series are exactly for this: who you are, what your business does, and what a good outcome looks like. The AI guesses less when it knows more.

Then test it, and fix it as it runs. It won't be right the first time. That's the iterate half of integrate.

What if I don't understand something while building?

Ask. You don't need to already know what an API is or how two tools connect. Tell the AI you don't understand and go back and forth with it the way you would with a coworker.

That back and forth is also how the workflow ends up fitting your business rather than a generic version of it.

The whole series, in one idea

Every workflow in this library was built this way. Albus and the morning brief, Ella in my inbox, Snape and the relationship records, Pareto and the SOPs, Bibbidi and the repurposing, the onboarding agent. All of them. Blueprint what happens, organize where it lives, systematize it into a recipe, assign each step to AI or a person, then build and keep fixing.

Four of those five steps happen before you open an automation tool. That's the part most people skip, and it's why most automations don't survive their first month.

That's the end of the series.

I've had so much fun making these. I'm going to miss it.

If you've followed along, thank you. Every one of the 31 is still in the library, with the prompts. And if you'd rather have this built for you than build it yourself, that's what the systems audit is for.

Browse all 31 workflows at webuildaisystems.com/workflows. Book a systems audit at webuildaisystems.com.