Daily n8n Digest

MB

Automate phone answering — quick briefing

Reddit / r/n8n roundup · Apr 27, 2026

You asked how to automate phone answering with n8n. Community responses clustered around three trade-offs: turnkey voice platforms (less control), modular stacks (more control, more code), and focusing on process — not just tooling — to recover missed calls.

Top Stories

Recommended stack: vapi.ai + n8n

Best fit for n8n workflows that want real-time voice without reinventing STT/TTS inside n8n.

• vapi.ai webhook fires on call-start with {caller_id, transcript_so_far}.
• n8n acts as the workflow brain: webhook → DB/HTTP lookups → LLM decision → return text to vapi to speak.
• retellai works for voice-only but gives less control; watch for a known retellai gotcha — you must echo tool_call_id in the webhook response or audio output breaks.
• Twilio + Deepgram + OpenAI Realtime = maximum control, maximum code; avoid unless you need deep customization.

Minimal n8n node shape: Webhook (vapi/retellai) → HTTP/DB lookups (caller history/calendar/KB) → LLM node (compose reply) → Respond to webhook (text → spoken back).

Community Buzz

Turbulent-Toe-365 explained the vapi.ai pattern and implementation details, plus the retellai tool-call_id gotcha. They also suggested using vapi’s callback scheduling for missed calls and having n8n queue an SMS via Twilio within ~30s.

Puzzleheaded-Rip2411 argued the real problem is accountability: most automations just log calls or send a text and stop. The owners should treat missed calls as a revenue leak — the fix is instant callback attempts, quick qualification, then book or nurture.

echowin pitched a proprietary tool as simpler and more production-ready than stitching n8n workflows; another commenter noted that can be fine if you don’t plan to expand the system later.

Tone snapshot: helpful technical guidance + healthy skepticism about “demo” workflows that don’t solve the business process.

Quick Hits

• Choose vapi.ai if you want n8n to decide responses in real time without handling STT/TTS yourself.
• If you need maximum control (custom STT/TTS, low latency), use Twilio + Deepgram + OpenAI Realtime — expect more engineering work.
• Don’t build STT/TTS inside n8n — treat n8n as the brain only.
• Test with real calls end-to-end (retellai tool_call_id is an easy-to-miss integration bug).
• If missed calls matter financially: implement a 30-second response rule — attempt instant callback, qualify, then book or nurture.
• Ask yourself: inbound support, sales qualification, or appointment booking? The stack and SLA change depending on that answer. Read the thread

Want this turned into a quick architecture checklist or an n8n starter workflow JSON for vapi.ai? Reply with your use case (support / sales / bookings) and I’ll draft it.