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.
| Trigger | Fires when | Typical use |
|---|---|---|
| booking_created | A booking is created | Instant confirmation message |
| before_booking | offset_minutes before the booking start | Preparation instructions, documents to bring |
| after_booking | offset_minutes after the booking start | Follow-up, feedback request, rebooking offer |
| no_show | The booking window passed without arrival | No-show policy notice, rebooking link |
| cancelled | A booking is cancelled | Cancellation 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.