n8n Community Digest
Automate phone answering — highlights from the r/n8n thread (April 27, 2026)
Major highlights
The top replies split into two camps: pragmatic integrations that treat n8n as the "workflow brain" and heavier, full-control stacks for realtime voice. Key recommendations and gotchas are below.
Top technical guidance (summary)
- vapi.ai — recommended as the best n8n fit: webhook fires on call-start with {caller_id, transcript_so_far}. n8n responds with text and vapi speaks it back.
- retellai — fine for voice-only, but gives less control; watch for a strict webhook JSON shape (you must echo tool_call_id or responses break).
- Twilio + Deepgram + OpenAI Realtime — most control and complexity (more code), suited for teams that need full realtime pipelines.
- Role for n8n — use it as the workflow brain only. Avoid doing STT/TTS in n8n; have the telephony/voice layer handle audio and send structured events to n8n.
Suggested minimal n8n workflow:
- Webhook node (incoming event from vapi/retellai)
- HTTP/DB lookup (caller history, calendar, KB)
- LLM node (generate reply)
- Respond to webhook (text → spoken back to caller)
Pro tip: test a real call round-trip before assuming the integration is working (especially with retellai's strict webhook format).
Trending community conversations
Apr 27, 2026 · 1 upvote
Detailed stack advice: prefers vapi.ai for n8n workflows, explains how webhooks pass caller/transcript, gives a minimal node list for n8n, and flags retellai's webhook JSON quirk. Also notes vapi supports callback scheduling for missed calls.
Apr 27, 2026 · 2 upvotes
Focuses on process: missed calls are a revenue leak. Automation isn't the fix by itself — you need accountability, instant callback attempts (within ~30s), qualification, and booking/nurturing to actually recover revenue.
Apr 27, 2026 · 1 upvote
Short pitch: "Why not use a tool like ours?" Argues purpose-built products scale better than stitched-together n8n demos. A reply notes that standalone tools are fine if you don't plan to extend the system later.
Apr 27, 2026 · 1 upvote
"Not into that anymore, sucks." Short and candid.
Apr 27, 2026 · 3 upvotes
A bit of nostalgia: "I'm old enough to remember being attached to a wall while answering the phone. We don't do that shit anymore."
Quick updates
- Testing note: always validate webhook round-trip with a live call—some providers require specific JSON fields (e.g., tool_call_id).
- n8n's sweet spot: orchestration and business logic (lookups, qualification, scheduling). Let a voice provider handle STT/TTS.
- If recovering missed-call revenue is the goal: implement an instant-callback + qualification + booking flow, not just logging.
- Consider trade-offs: quick-to-deploy hosted tools vs. full-control builds (Twilio + Deepgram + OpenAI Realtime).
Which do you need: inbound support, sales qualification, or appointment booking? The recommended stack shifts by use case — reply to the thread to get tailored advice.
You're receiving this because you asked for a curated digest of r/n8n discussions. View the original thread or reply on Reddit.
Top comments (0)