Credentials. Each connected app stores its credentials in n8n; restrict who can open the instance.
Who it is forA team that wants AI to do the busywork on emails, tickets or leads but never act without a check.
The problemFully automatic AI flows are risky and fully manual work is slow.
The outcomeA multi-step workflow where the AI step proposes an action and waits for approval before the final step runs.
What you need first
- Docker for the self-hosted quick start
- Accounts or API keys for the apps and models you connect
Steps
- Start from a template in the 9,000+ workflow library or a blank canvas
- Add a trigger, then an AI step using OpenAI, Anthropic, Google or an open-source model
- Give the agent tools from your integrations
- Insert a human approval step before any step that sends or changes data
- Run it on test data and read the execution log before turning it on
Prompt for your agent
In my n8n-io/n8n instance, build a workflow that triggers on <event>, uses <model> to draft <output>, waits for my approval, then <final action>. Explain each node and where credentials are stored.
Caveat.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for n8n-io/n8n and "Build an AI agent workflow with a human approval step"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer