How do I replace ManyChat with Claude + n8n?
Three steps. About two hours including Meta app review.
Step 1: Self-host n8n
bash
# Local dev
npx n8n
# Production via Docker
docker run -it --rm --name n8n -p 5678:5678 \
-v n8n_data:/home/node/.n8n \
docker.n8n.io/n8nio/n8n
The official repo is github.com/n8n-io/n8n — 187k stars.
Step 2: Get an Instagram / Messenger webhook
Create a Meta app at developers.facebook.com, add the Instagram Messaging product, point the webhook at https://your-n8n.com/webhook/ig-dm. The Meta side is free.
Step 3: Add a Claude credential in n8n
In n8n: Credentials → New → Anthropic. Paste your Claude API key.
Step 4: Build the auto-reply workflow
The minimum viable replacement is five nodes:
[Webhook: IG DM in]
↓
[Function: extract user message + context]
↓
[Anthropic Claude: generate reply]
↓
[IF: contains keyword? send guide link]
↓
[HTTP: POST reply via Meta Graph API]
That is the whole thing. No flow builder, no contact-counting, no per-active-user surcharge.
Step 5: Add a knowledge base via the Anthropic system prompt
This is where Claude blows past ManyChat:
json
{
"model": "claude-sonnet-4-6",
"system": "You are the Nanoflow DM assistant. The product list, the FAQ, and the guide URLs are below. Reply in 1-2 sentences max. Always end with a guide link if the user mentioned [keyword].",
"max_tokens": 200
}
You drop your entire FAQ into the system prompt. Claude grounds every reply on it. ManyChat's bot logic is hand-wired keyword trees — Claude just reads.
Step 6: Wire keyword routing for lead magnets
Match the ManyChat "comment a keyword for the link" pattern with one Function node:
javascript
const msg = $input.item.json.message.toLowerCase();
const keywords = {
"ai": "https://nanoflow.io/#/guides/wan2gp-killed-runway",
"voice": "https://nanoflow.io/#/guides/qwen-voice-killed-elevenlabs",
"design": "https://nanoflow.io/#/guides/impeccable-honest-take",
};
for (const k of Object.keys(keywords)) {
if (msg.includes(k)) return { url: keywords[k] };
}
return { url: null };
What is the Claude + n8n replacement stack?
It is two components. n8n is a fair-code workflow automation platform with 187k GitHub stars — described in the README as "the flexibility of code with the speed of no-code". Claude is Anthropic's LLM API.
Wire them together: n8n receives the webhook from Meta, calls Claude for the reply, posts back to Meta. Five nodes, infinite flexibility.
Is the Claude + n8n stack really cheaper than ManyChat?
Yes, by a lot. Run the math on a real account with 5,000 monthly active contacts and a few thousand DM exchanges per month:
| Stack | Monthly cost |
|---|---|
| ManyChat Pro (2,500 contacts) + AI add-on + overage to 5,000 | ~$163 |
| n8n self-hosted + Claude API (Sonnet, ~10k DMs) | ~$30-50 |
| n8n Cloud Pro + Claude API | ~$50-70 |
ManyChat's March 2026 pricing change cut the free tier from 1,000 contacts to 25 — a 97.5% reduction. Anyone doing serious DM volume now starts at $39+/month minimum.
How is Claude + n8n different from ManyChat?
Three differences:
- Replies are smarter. Claude grounds every response in your FAQ via the system prompt. ManyChat's flow builder is keyword trees — they fail the moment a user types something off-script.
- No active-contact billing. ManyChat charges per active contact. Claude + n8n charges per token, which is dramatically cheaper at scale because most contacts only DM once or twice.
- You own the workflow. n8n is fair-code on GitHub. Export the JSON, run it anywhere.
What's the catch?
- You build it once. ManyChat ships a flow builder UI. n8n gives you nodes you wire together. Budget 4-6 hours for the first version.
- Meta webhook auth is fiddly. First-time Meta app setup takes longer than the n8n part. Once configured, it stays solid.
- You handle compliance and rate limits. ManyChat handles Meta rate limits for you. With direct API access you build retry/backoff yourself.
Bottom line
If you are paying ManyChat $40-200+/month, the Claude + n8n stack pays back the build time inside of one billing cycle. The replies are better, the cost scales with tokens not active contacts, and you own the entire pipeline. The only people who should stay on ManyChat are teams who genuinely cannot self-host anything.
Related Nanoflow guides
Want a hand?
Book a 30-min call.
Walk through your stack with us. We'll find the bottleneck and map out the exact wiring you need — free.