Missed‑call text back in n8n and Twilio: why the Dial action beats the status callback

Описание и применение

Автоматический сценарий n8n, использующий <Dial> с action‑callback в Twilio, позволяет отправлять SMS при пропущенных звонках, даже если номер перенаправлен на мобильный.

Задача

When a business forwards its Twilio number to a mobile, the call is marked as answered by Twilio, so a missed‑call text automation never triggers.

Результат

The workflow reliably sends a missed‑call text even when the call is forwarded to a mobile phone, by using the <Dial> verb’s action callback instead of the status callback.

Рабочий процесс

• Create a TwiML Bin that dials the mobile number with timeout="12" and action="https://YOUR‑N8N‑HOST/webhook/missed‑call"
• Configure an n8n Webhook node at path missed‑call to receive the POST from Twilio
• Use a Set node to pass user‑editable values (businessName, bookingLink, twilioNumber, etc.)
• Respond immediately to Twilio with TwiML that says a short message if DialCallStatus is no-answer, busy, or failed, otherwise hang up
• Add an IF node that checks the AccountSid, DialCallStatus, and From number to filter out answered calls, anonymous numbers, and unauthorized requests
• Add a second IF node that checks the current hour against openHour and closeHour to decide daytime or after‑hours text
• Use a Twilio SMS node to send the constructed text to the caller
• Append a row to Google Sheets with call details

Доказательства

If they don't pick up, the mobile's voicemail answers. From Twilio's point of view the forwarded call was answered, so the status is completed, and the automation never fires.

Источник

Twilio decides what counts as "missed," and n8n replies with TwiML in the same request.

Источник

Twilio POSTs the action request as application/x-www-form-urlencoded. The fields we care about are DialCallStatus, From, To, CallSid and AccountSid.

Источник