Module 6 · Run · Lesson 2 of 4
Build one automation that reads a lead, drafts a reply with Claude, and waits for your approval before it sends.
Deliverable: Build one working automation that handles a repeat task end-to-end - for example, an inbound lead that Claude drafts a reply to, that you approve before it sends - and write a one-paragraph runbook explaining how it works.
Part of the Make First Path
Pass this stage's gate ($10,000 cumulative gross profit, running in under 10 hours a week) and you earn your First $10K.
See the Run stage →Build one workflow that does a repeat task end-to-end with a human approval step - an inbound lead, a reply Claude drafts, your approval, then it sends.
by Anthropic · 20 min
Anthropic's own advice on keeping agents simple, composable, and human-in-the-loop - the model for the approval step you're about to build.
by Nate Herk | AI Automation · 20 min
The AI Agent node segment shows how to wire an approval step into a workflow - watch just that part of the masterclass.
An automation that runs by itself sounds great until it does something wrong by itself. That is why this lesson insists on a human approval step. You are not building a robot that replaces you. You are building a workflow that does the boring 90 percent of a task and hands you the last 10 percent to check.
Think about a lead who fills out a form on your site. Right now you probably read it, think about what to say, and type a reply. That thinking-and-typing part is where you add value. The reading and drafting can happen without you. So the workflow you build this lesson reads the lead, drafts a reply with Claude, and then stops and waits for you to say yes before anything gets sent.
This matters for two reasons. First, mistakes happen, and a human checking before something goes out to a real customer catches them before they cost you a customer or your reputation. Second, it is genuinely how the best automations get built: small, checkable steps, not one giant system you can’t inspect.
Get this pattern right once and you can reuse it everywhere - support replies, follow-up messages, order confirmations. It is one of the most useful skills in the whole Run stage.
Use this conversation to design your workflow on paper before you build anything in n8n. If you get stuck once you’re building, come back to this same conversation and describe the error - Claude can help you debug a step without building the whole thing for you.
I'm a teenager building my first AI agent workflow: a repeat task in my business that should run end-to-end with a human approval step before anything goes out. Don't design the workflow for me. Ask me what the trigger is, what the AI should draft, what could go wrong if it sent something without a human checking first, and where exactly the approval step should sit. Help me think through it question by question. If I come back later with an error message from my workflow, help me understand what it means and ask me what I've already tried before suggesting a fix. Make
Build one working automation that handles a repeat task end-to-end - for example, an inbound lead that Claude drafts a reply to, that you approve before it sends - and write a one-paragraph runbook explaining how it works.
Checkpoint
Your automation has run at least 5 times, and you have logged the hours it saved you.
Videos in this lesson are by Anthropic and Nate Herk | AI Automation, embedded from YouTube with the official player. Make First curates and does not own them, and will remove any embed on a creator's request. Read how we curate →
Want a coach who won't do it for you?
Join the founding cohort and work directly with the founder through every gate.
Join the founding cohort