Skip to main content

Send Aloware SMS confirmations, reminders, and no-show rebooking for appointments

Workflow preview

Workflow preview
100%
Send Aloware SMS confirmations, reminders, and no-show rebooking for appointments preview
Open on n8n.io

1. Workflow Overview

Description Automate your entire patient appointment communication lifecycle: instant booking confirmation, timed reminders, and automatic no show detection with re booking outreach — all powered b...

Best for

  • Support Chatbot automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.webhook, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.wait, n8n-nodes-base.if, n8n-nodes-base.noop

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Maxim Dudnik.

Original n8n.io source

1.1 Workflow description

Title
Send Aloware SMS confirmations, reminders, and no-show rebooking for appointments
Workflow name
Send Aloware SMS confirmations, reminders, and no-show rebooking for appointments

Description

Automate your entire patient appointment communication lifecycle: instant booking confirmation, timed reminders, and automatic no-show detection with re-booking outreach — all powered by Aloware sequences and n8n. No-shows cost healthcare practices an estimated $150 billion per year in the US alone. This workflow tackles the problem end-to-end by confirming appointments the moment they're booked, sending graduated reminders leading up to the visit, and automatically re-engaging patients who don't show up.

How it works

  1. A Webhook receives new appointment data from your booking system (Calendly, Acuity Scheduling, Jane App, SimplePractice, Mindbody, or any system that sends webhooks).
  2. A Set node normalizes the payload — patient phone, name, email, appointment type, date/time (formatted for SMS), provider name, and appointment ID.
  3. An HTTP Request creates or updates the patient contact in Aloware with appointment type and date stored in custom fields and notes.
  4. A second HTTP Request sends an instant confirmation SMS: "Your {appointment type} is confirmed for {date} at {time}. Location: {address}. Reply CANCEL or RESCHEDULE."
  5. An HTTP Request enrolls the patient in a timed Aloware Reminder Sequence (you configure this in Aloware to send reminders at 48h, 24h, and 2h before the appointment).
  6. A Wait node pauses execution until 1 hour after the scheduled appointment time.
  7. An HTTP Request checks the contact's tags in Aloware to detect whether a "no-show" tag has been applied.
  8. An IF node routes:
  • No-show detected → enrolls in a No-Show Re-booking Sequence (e.g., "We missed you today — reply to rebook").
  • Appointment completed → no further action.

How to use

  1. Import the JSON into n8n.
  2. Add these n8n Variables: ALOWARE_API_TOKEN, ALOWARE_LINE_PHONE, ALOWARE_REMINDER_SEQUENCE_ID, ALOWARE_NOSHOW_SEQUENCE_ID, PRACTICE_NAME, and PRACTICE_ADDRESS.
  3. In Aloware, create two Sequences:

Reminder Sequence: steps at 48h, 24h, and 2h before appointment (SMS reminders). No-Show Sequence: re-booking outreach (SMS → wait 1 day → call → SMS).

Configure your booking system's webhook to POST to this workflow's URL (Calendly → Webhooks, Acuity → API Webhooks, etc.). Set up a process in Aloware (or your EHR) to tag contacts as "no-show" when they miss their appointment — the workflow checks for this tag. Activate and test with a sample booking.

Requirements

Aloware account with API access and an outbound line Booking/scheduling system that supports webhooks (Calendly, Acuity, Jane App, SimplePractice, Mindbody, etc.) A process to apply a no-show tag in Aloware when patients miss appointments (manual or automated via your EHR)

Customising this workflow

Edit the confirmation SMS to include prep instructions (e.g., "Please arrive 15 minutes early" or "Remember to fast before your blood work"). Add a Slack or email notification to front-desk staff when a no-show is detected. Add an additional branch for cancellation handling — if the patient replies CANCEL, disenroll from the reminder sequence and notify the scheduler. Adjust the Wait node timing if your practice wants to check for no-shows immediately after the appointment window rather than 1 hour later.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Workflow Overview

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Book & Confirm

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Reminder Sequence

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - No-Show Detection

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Reminder Tip

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Booking System: Appointment Created

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2

Block 7 - Normalize Appointment Data

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Aloware: Create or Update Patient Contact

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 9 - Aloware: Send Booking Confirmation SMS

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 10 - Aloware: Enroll in Reminder Sequence

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 11 - Wait Until After Appointment

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 12 - Aloware: Check If Appointment Completed

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 13 - Was It a No-Show?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 14 - Aloware: Enroll in No-Show Re-booking Sequence

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 15 - Appointment Completed — No Action

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

3. Summary Table

Workflow Send Aloware SMS confirmations, reminders, and no-show rebooking for appointments
Complexity advanced
Nodes 15
Categories Support Chatbot
Author Maxim Dudnik
Published 13 Apr 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15021/15021.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Send Aloware SMS confirmations, reminders, and no-show rebooking for appointments do?

Description Automate your entire patient appointment communication lifecycle: instant booking confirmation, timed reminders, and automatic no show detection with re booking outreach — all powered b...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support Chatbot use case.