Ship Lean Workflow Human approval

n8n AI agent workflow.

Use n8n as the trigger and routing layer around one scoped AI judgment step.

Keep the agent focused. Keep approval where consequences exist. Let n8n own the repeatable run.

workflow/safe-agent

$ agent job

score query, draft response, classify lead

$ approval gate

ok no public action without human review

Workflow shape

Five steps. One judgment call.

STEP_01

Trigger

n8n starts the run from a form, schedule, video upload, Search Console export, webhook, or status change.

STEP_02

Context

n8n gathers the transcript, CSV, task, URL, repo link, customer note, or brief the agent needs.

STEP_03

Agent task

Claude, OpenAI, Anthropic, or another model handles one judgment-heavy job: draft, classify, score, plan, or review.

STEP_04

Approval

A human approves anything public, expensive, customer-facing, production-facing, or brand-sensitive.

STEP_05

Route

n8n saves the result to Notion, GitHub, email, Slack, a CMS, or a publishing queue.

When this workflow makes sense

Use this pattern when the work repeats, needs multiple app handoffs, and has one judgment-heavy step. Good examples: content brief creation, lead triage, Search Console opportunity scoring, support summary routing, and workflow planning.

Which search intent this page answers

This is the owner page for n8n AI agent workflow and agentic workflow examples. If you need the shorter definition, start with what an n8n AI agent is. If you want the build sequence, use the n8n AI agent tutorial. If you are deciding between an agent and plain automation, read n8n AI agent vs workflow automation. And if you are not sure you need n8n at all, start with ChatGPT vs n8n.

Query Answer
n8n ai agent workflow Use n8n for the trigger, context gathering, routing, retries, logs, and approvals around one AI judgment step.
n8n agentic workflow The workflow becomes agentic when the model can choose tools, inspect results, and return a structured decision.
n8n multi agent workflow Start with one agent and one job. Add more agents only after a single scoped agent cannot handle the workflow.

What not to do

Do not put the whole business process inside one giant agent prompt. n8n should own the run history, retries, credentials, logs, and routing. The agent should own one reasoning step.

Starter file

Download the n8n human approval workflow JSON and replace the decision stub with your AI Agent, Claude, or OpenAI node.

The same proof asset is also published on GitHub as an importable template: n8n AI lead qualification workflow with human approval.

Real example source

This public starter is based on a real lead-routing pattern: webhook intake, lead enrichment, AI qualification, structured parsing, and routing into follow-up paths. The private workflow stays private; the public file keeps the reusable shape without credentials, personal data, or business-specific routing.