Daily n8n Digest

Automate phone answering — what n8n folks actually use

A quick digest from r/n8n: stacks, gotchas, and the real business metrics that matter

Top Stories

Best practical stack: vapi.ai + n8n

Several responders recommend keeping speech (STT/TTS) and real-time audio at the platform layer (vapi.ai or retellai) and using n8n strictly as the workflow brain.

• vapi.ai — webhook fires on call-start with {caller_id, transcript_so_far}; n8n returns text that vapi speaks back. Clean fit for n8n workflows.
• retellai — works for voice-only but gives less control and has a webhook JSON shape gotcha (you must echo the tool_call_id or the caller hears gibberish).
• Full control (more code) — Twilio + Deepgram + OpenAI Realtime. Powerful, but heavier to build and maintain.

Minimal n8n workflow pattern recommended:

• Webhook node (receive call events)
• HTTP/DB lookup (caller history, calendar, KB)
• LLM node (decide response / qualify)
• Respond to webhook (return text → TTS via platform)

Product tip: vapi offers built-in callback scheduling for missed calls; n8n can listen for missed-call webhooks and queue an SMS/Twilio callback within ~30s to recover potential revenue.

Community Buzz

Selected comments from the thread (source)

"Honest answer is that retellai is fine for the voice-only path but limits you on the n8n side... vapi.ai — best n8n fit." — Turbulent-Toe-365 (1 upvote)

"You don’t actually need fancy automation for this. You need real accountability on missed calls... Speed is everything." — Puzzleheaded-Rip2411 (2 upvotes)

"Why not use a tool like ours? Much simpler than rigging together n8n workflows that make for good demos but don't scale in production." — echowin (1 upvote)

"not into that anymore, sucks" — lucasbennett_1 (1 upvote)

"I'm old enough to remember being attached to a wall while answering the phone. We don't do that shit anymore." — TheDailySpank (3 upvotes)

Quick Hits

Don’t do STT/TTS in n8n

Test with a real call (not just simulated webhooks)

Echo required fields (tool_call_id) for retellai

Handle missed calls as revenue leaks — 30s rule

Decide: real-time voice vs batch processing

Implementation checklist

• Pick your voice platform: vapi.ai for n8n-friendly webhooks, or Twilio stack for full control.
• Design n8n as the "brain": use webhook → lookup → LLM → respond.
• Build missed-call workflow: schedule callback + SMS within 30s for higher recovery.
• Run end-to-end live-call tests before rollout.

Read the thread

Want this tailored to your use case? Reply with what you need the system to do (inbound support, sales qualification, appointment booking) and we'll sketch a recommended stack and n8n workflow.