Buildler Booking / Features / Automations

Features

Automations

Event, condition, action — follow-ups, rebooking prompts and recovery when someone cancels.

01

Event → condition → action

A small model that stays readable months later.

02

Follow-ups and recovery

Prompt a rebook when a slot frees, without manual chasing.

03

Webhooks and apps

Signed webhooks in core; Zapier, Make and n8n when you need them.

Why it matters

The diary should continue working after the click.

Automations pick up after confirmation: thank-you sequences, rebooking prompts, and recovery when someone cancels. Email-only automations are available early; the fuller set lands on Business and Ultimate.

Nothing here disables the free plugin if you never buy a plan. Automations add capability; they are not a countdown clock on the licence.

Stay connected to the rest of the stack

Without copy-paste exports.

Signed webhooks ship in core so your CRM or practice system can react to bookings. Zapier, Make and n8n apps cover teams that already live in those tools.

Each automation still respects the same delivery log and retry behaviour as ordinary reminders, so failures are visible rather than silent.

How it works
  1. 01

    Pick an event

    Booking created, cancelled, completed, and similar.

  2. 02

    Add a condition

    Service, location, or timing — keep it narrow.

  3. 03

    Choose an action

    Email, SMS where licensed, or a signed webhook.

Start with the free version.

Unlimited appointments, no expiry, no card.

See pricing Read the docs