Event → condition → action
A small model that stays readable months later.
Buildler Booking / Features / Automations
Event, condition, action — follow-ups, rebooking prompts and recovery when someone cancels.
A small model that stays readable months later.
Prompt a rebook when a slot frees, without manual chasing.
Signed webhooks in core; Zapier, Make and n8n when you need them.
Why it matters
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
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.
Booking created, cancelled, completed, and similar.
Service, location, or timing — keep it narrow.
Email, SMS where licensed, or a signed webhook.
Related
Working hours, buffers, capacity, and timezone-correct slots — so the diary matches the chair.
Stripe, deposits, balances, refunds and coupons — without touching card data yourself.
Templates, a delivery log, retries and cron health — so messages arrive, or you know why not.
Reschedule and cancel without an account — through signed links, not a shared password.
Day, week, month and staff timeline views, with drag to reschedule — and locks that prevent double booking.
Multiple forms, configurable steps, and a live editor — placed as block, shortcode, Elementor or Bricks.
Unlimited appointments, no expiry, no card.