Missed-call text-back: an n8n workflow design for clinics and small businesses
A caller who gets no answer often rings the next business on the list. This workflow replies to them with a text right away. It listens for call-status notifications from Twilio, lets through only the calls that went unanswered, builds a message that changes after hours, sends it, and logs the call to your CRM. It sends at most one text to each caller every 4 hours. The canvas below is a design, not a download.
The workflow canvas
Personal 01 - Missed Call Text-Back
Steps, in order
In the sample run
Starts the workflow. Twilio sends a call-status notification to this address every time a call ends.
You would set
- MethodPOST
- Set as the Twilio voice status callback
- Point the Twilio voice status callback (POST) at this workflow. Only no-answer, busy and failed calls continue.
- Cooldown: one text per caller every 4 hours. Wording changes after hours.
IllustrationThe ticks mark the steps of a sample run, drawn as an example.
- Starts it
- Calls or sends
- Logic and settings
- Sample run
Use the arrow keys to move between steps. The selected step is described after the canvas.
What is built into the design
- Only no-answer, busy and failed calls continue. Answered calls stop at the first check.
- One text per caller every 4 hours, so repeat callers are not spammed.
- The wording changes after hours.
What you need
- 01A Twilio phone number
- 02An n8n instance, hosted by you or by n8n
- 03A CRM or sheet with an API to log calls to
How you would set it up
- 01
Point the Twilio voice status callback (a POST request) at the workflow’s webhook address.
- 02
In the Config step, set the business name, opening hours and the wording of the text.
- 03
Set the CRM address the last step writes to.
- 04
Use the Test workflow button with a sample call, then switch the workflow on.
Add these before it touches real customers
- An error workflow that alerts a person if Twilio or the CRM call fails, so a failure is never silent.
- An opt-out line in the text, and a list of numbers that must never be texted again.
- A test with an answered call, a busy call and a repeat caller, with the result written down.
Stay safe
- Keep health details out of the text. "Sorry we missed your call, how can we help?" is enough.
- If the caller could be a patient, check with your compliance adviser whether your SMS provider will sign a Business Associate Agreement (BAA) and whether this use is allowed.
Texting and emailing rules differ by country and by who you are contacting. Check yours with a qualified adviser. This page is not legal advice.
Questions
Is this a download I can import into n8n?
Not yet. This page shows the design as a drawn canvas, so you can see how the steps connect. It has not been built and tested end to end, and it is not a screenshot of a live n8n.
Why a cooldown?
Without one, a caller who rings three times gets three texts. A cooldown of one text per caller every 4 hours keeps the message helpful instead of annoying.
Can I have this built for my business?
Yes. I build AI integrations, bots and automations. Tell me what you use for calls and records, and I will say what it would take.
Want this built into your own workflow?
Tell me what you use today and what you do by hand. I will say what is safe to automate, what needs a person, and roughly what it would take. I reply within 24 hours.