n8n Missed Call Text-Back Workflow with Twilio & Email Alerts
n8n Missed Call Text-Back Workflow with Twilio & Email Alerts
Regular price
£62.99
Regular price
£62.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
n8n Missed Call Text-Back Workflow with Twilio & Email Alerts
Regular price
£62.99
Regular price
£62.99
Sale price
Unit price
/
per
Auto-text missed callers with Twilio—plus approvals and audit logs
This n8n workflow instantly handles missed-call webhook events, looks up the caller in your n8n Data Table, and sends a Twilio SMS “text-back” message—while logging outcomes and notifying a dispatcher by email (with approval required for after-hours calls).
What this workflow does
- Receives missed call events via Webhook: accepts a POST request containing the caller details.
- Normalizes and validates the caller number: standardizes the incoming phone number, sets the call timestamp, and determines whether it happened after business hours.
- Rejects invalid/missing numbers safely: if the phone number is missing or invalid, it responds with HTTP 400, records the rejected event in an n8n Data Table, and emails the dispatcher.
- Responds immediately for valid events: for valid numbers, it responds with HTTP 202 and proceeds without delaying the webhook response.
- Looks up callers in an n8n Data Table: checks demo_contacts to decide whether the caller is a known customer or a first-time caller.
- After-hours approval gate: if the call is outside business hours, it emails an approval request to the dispatcher and only sends the text-back after approval.
- Sends different SMS content: builds a tailored Twilio SMS for known customers vs. first-time callers and sends it back to the caller.
- Logs results and escalates on failure: writes the SMS result to demo_missed_calls and emails the dispatcher with either a confirmation (sent) or an action-required alert (failed).
Use cases
- Customer support lines that need an immediate missed-call text-back with the right messaging per caller type.
- Operations teams requiring dispatcher oversight for after-hours outreach.
- Teams that want traceability by logging each call and SMS outcome to n8n Data Tables.
Technical details
- Nodes/stack: Webhook, if, set, Twilio, Data Table, Email Send.
-
Required Data Tables:
demo_contacts(phone, name) anddemo_missed_calls(phone, caller_type, status, detail, called_at). - Twilio setup: add Twilio credentials, provision/verify the sending phone number, and configure the workflow’s Twilio “from” number.
