Automations
Build supported stay workflows with clear approval expectations.
On this page
Trigger → condition → action
A trigger determines when a rule is considered. Eligibility conditions include workspace, booking status and dates. The action describes the intended outcome. Selecting a label does not make an unsupported channel or condition operational.
Create and manage a rule
Owners and admins manage, run and approve rules; members can read them.
- 1Open Automations and choose a supported template or creation action.
- 2Choose the trigger and supported action.
- 3Review channel and approval mode.
- 4Save and set the rule active when ready.
- 5Review run history to confirm what occurred.
Supported stay triggers
Booking confirmation considers confirmed bookings created within the last 24 hours. Three days before check-in uses check-in date +3 days from today; check-in day uses today. One day before checkout uses checkout tomorrow; after checkout uses yesterday. Date comparisons use UTC days.
Eligible statuses
Date-based stay triggers consider confirmed, in stay, checkout soon and completed; inquiry and cancelled are excluded. Check that the recorded status and dates match the intended rule.
Automatic actions and approval
Supported guest-message automation uses email only when its setup and eligibility allow it. Approval modes can draft for review, automate eligible actions or escalate. Host notifications are internal. A successful run does not necessarily prove a guest received an email. Scheduled lead follow-up remains unavailable.