n8n WhatsApp with Live Context in 2026

An r/n8n WhatsApp Automation thread (23 upvotes, 35 comments) surfaced the production gap that bites every WhatsApp bot at scale: scripted answers cover 60-70% of questions and break on the rest. Adding live web context closes the gap; n8n + Scavio is the stack.

Why most WhatsApp bots disappoint

Two failure modes:

• Template-only. The bot answers from a fixed FAQ. Anything outside the script either loops the user back to FAQs or escalates to email.
• LLM with no grounding. The bot pipes the question to an LLM with no tools. Hallucinations on pricing, hours, addresses, product specs.

The right design is hybrid: scripted for known intents, grounded LLM for free-form. The grounding layer is what most stacks skip.

The n8n hybrid stack

Components:

• n8n self-host (free) or Cloud Starter (EUR 20/mo)
• WhatsApp Business API (Meta-verified, ~$0.005-0.10/conversation)
• Scavio HTTP node ($30/mo for 7K credits)
• LLM node (Claude or OpenAI, pennies per response)

The flow

1. WhatsApp Trigger fires on inbound message
2. Switch node classifies intent: scripted vs free-form
3. Scripted path: static response from FAQ table
4. Free-form path: Scavio HTTP node searches site:yourcompany.com
5. LLM node grounds the answer in top-3 Scavio results
6. WhatsApp Send returns the grounded answer with source links

The Scavio HTTP node config

{
  "method": "POST",
  "url": "https://api.scavio.dev/api/v1/search",
  "headers": { "x-api-key": "<YOUR_KEY>" },
  "body": {
    "query": "{{$json.messages[0].text.body}} site:yourcompany.com"
  }
}

The LLM grounding prompt

Answer the user's question using ONLY these sources from our website.
If the sources don't answer, say "Let me connect you to a team member."

Sources:
{{$json.organic_results.slice(0,3).map(r => '- ' + r.title + ': ' + r.snippet + ' (' + r.link + ')').join('\\n')}}

Question: {{$node['WhatsApp Trigger'].json.messages[0].text.body}}

Per-conversation cost

Verified pricing (2026-04):

• WA Business API: $0.005-0.10 per 24-hour conversation window (varies by country and category)
• Scavio: 1-2 search calls per free-form question = $0.004-0.009
• LLM: ~$0.003-0.015 per response on Claude Sonnet

Total per free-form conversation: $0.012-0.124. Compares favorably with email support cost ($1-5/ticket) for deflectable questions.

The setup gotcha

WhatsApp Business API requires a verified Meta business account and message-template approval for outbound sends. The setup takes 1-3 business days. Plan for that lag in any "ship the WA bot tomorrow" estimate.

Inbound replies (the path this stack uses) don't require template approval — only outbound proactive sends do. So the grounded-reply use case ships on day one of API access.

What scripted vs free-form looks like in practice

Scripted (regex match -> fixed response):

• "Hours" -> static hours card
• "Pricing" -> pricing table or link
• "Address" -> static map link

Free-form (Scavio + LLM):

• "Do you ship to Argentina?" -> search shipping page, ground answer
• "Difference between Pro and Enterprise?" -> search comparison page, ground answer
• "Is this product compatible with X?" -> search docs, ground answer

Why n8n vs the alternatives

Wati and Respond.io ship faster (turnkey UI). The cost: locked to their flow builder, no code-when-you- need-it escape hatch. n8n + Scavio is the right call when the bot needs branching beyond the turnkey UI, custom integrations beyond their library, or self-hosted control.

The honest answer to the thread

Most production WhatsApp bots in 2024-2025 were template-only. The 2026 baseline includes grounded LLM responses for free-form questions. Stacks that ship the grounded path deflect more, frustrate users less, and cost about the same per conversation as the email support they replace.