Skip to content
Docs home

CORE CONCEPTS · UPDATED AUGUST 2026

Workflows & Automation

Trigger-based automation: messages sent before or after bookings, on booking creation, cancellation, or no-show — configured per service.

The trigger set

A workflow fires on one of five verified triggers: booking_created, before_booking, after_booking, no_show, and cancelled. The set is enforced at the database level — a workflow cannot be saved with a trigger outside this closed set.

TriggerFires whenTypical use
booking_createdA booking is createdInstant confirmation message
before_bookingoffset_minutes before the booking startPreparation instructions, documents to bring
after_bookingoffset_minutes after the booking startFollow-up, feedback request, rebooking offer
no_showThe booking window passed without arrivalNo-show policy notice, rebooking link
cancelledA booking is cancelledCancellation acknowledgment, reopen invitation

Configuring a workflow

Each workflow has a name, an enabled flag, a trigger, an offset in minutes (used by the before/after triggers), a channel (email or sms), an optional subject (email), a message body, and an optional service scoping. A workflow scoped to a service fires only for bookings of that service; an unscoped workflow fires for all bookings in the tenant.

How dispatch runs

Workflows are dispatched by a scheduled cron route that scans enabled workflows, resolves the target bookings for each trigger relative to the current time, and sends through the tenant's configured notification channels. Because dispatch is scheduled rather than instantaneous for time-relative triggers, message timing follows the schedule interval — plan offsets accordingly.

No free-form automation builder

QUE does not ship a visual multi-step automation builder. Automation is the verified trigger/offset/channel/service model described here. If your operation needs more complex branching, use outbound webhooks to route events into the workflow tool you already operate.

STILL READING

Something here still feels worth checking together.

This documentation describes the product exactly as it is implemented. If a behavior you expected is not here — or is here and does not match your deployment — tell the team. Implementation questions start on the contact page.