adegette shared this post · Apr 25
Nate Herkelman

Agentic Workflows Just Changed AI Automation Forever! (Claude Code)

Visual workflow automation requires you to drag nodes, configure each one, connect them, test, debug, and repeat.

Agentic workflows flip this completely.

You tell it what you want in plain English. The agent asks you the right questions and figures out the rest.

I just dropped a 20 minute YouTube video going over:
→ Self-healing: The agent debugs its own code when something breaks
→ Real natural language control: It interviews you first, then builds
→ Security baked in: LLMs review every code change for vulnerabilities
→ Instant integrations: Say the tool name, provide your API key, done

I also walk through the WAT Framework I use for building these:
1️⃣ Workflows — Markdown SOPs defining what to do
2️⃣ Agent — The brain that decides which workflows to execute
3️⃣ Tools — Python scripts for deterministic tasks

Plus a live build example: scraping dentist leads, enriching data, writing personalized outreach, and pushing it all to Google Sheets.

Key takeaway: You need to know how to communicate what you want clearly.

I also want to be clear. I don't think tech like this will "kill n8n". I think it's important to understand the differences and be able to pick the right tool for the job.

Link to the full video is in the comments 👇

346
Carlos Leon You can add a feedback loop with ETL solutions like Windsor ai, and make your Claude Code talk via MCP with the database, CRM, or analytics tool, so that it knows its performance and can adjust. Jan 28
Nolan Prayagsing What's your approach when the agent's "interview" phase misunderstands the requirement and builds the wrong workflow structure? Jan 26