Appointment reminder texts: an n8n workflow design for clinics
Each afternoon this workflow asks your scheduling system for tomorrow’s appointments, tidies each record, skips anyone without a mobile number, sends a reminder text and marks the appointment as reminded so nobody is texted twice. For a new business you change only two things: the scheduler address and the field mappings. The canvas below is a design with an example run drawn on it, not a live system.
The workflow canvas
Personal 02 - Appointment Reminders
Steps, in order
In the sample run
Starts the workflow every day at 4 pm.
You would set
- Scheduledaily, 16:00
- Time zone of the clinic
- Runs daily at 4 pm. Example run: 12 appointments tomorrow, 11 texted, 1 skipped (no mobile number).
- Per client: change the scheduler URL and the Normalize field mappings. Everything else stays the same.
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
- Runs once a day at 4 pm and looks at tomorrow’s appointments.
- Appointments with no mobile number are skipped, not guessed.
- Each sent reminder is marked, so a rerun does not text the same person twice.
What you need
- 01A scheduling system that can list appointments over an API
- 02A Twilio phone number
- 03An n8n instance
How you would set it up
- 01
Set the scheduler address in the "Get appointments" step.
- 02
Map the scheduler’s fields to the standard ones in the Normalize step: patient name, mobile number, date, time and place.
- 03
Set the reminder wording and the send time in Config.
- 04
Run a test with made-up appointments before using real ones.
Add these before it touches real customers
- An error workflow that alerts a person if the scheduler or Twilio call fails.
- An opt-out line, a list of people who must not be texted, and a check against it.
- Time zones for each location, so "4 pm" and "tomorrow" mean the right thing.
- A written test with a day that has no appointments, a day with a missing number and a rerun.
Stay safe
- Keep the text to the basics: the date, the time, the place and a way to confirm or cancel. Leave out the reason for the visit and any health detail.
- Check consent. Whether you may text a patient depends on your country and on what they agreed to.
- If patient information passes through Twilio or n8n, check with your compliance adviser which agreements you need. Hosting n8n yourself does not by itself make a workflow compliant.
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 the example run real?
No. "12 appointments, 11 texted, 1 skipped" is an example drawn on the canvas to show what a run looks like. It is not a result from a clinic.
Can I send these on WhatsApp instead of SMS?
In principle, but WhatsApp has its own rules: a 24-hour window for free-form messages, approved templates outside it, and a recorded opt-in. The WhatsApp checker and guide on this site explain them.
Why mark each reminder as sent?
Workflows get rerun after a failure. Without a mark, a rerun texts everyone again. Marking each sent reminder makes a rerun safe.
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.