Narrow a rule with conditions
A rule with no conditions fires for every booking that reaches it. Conditions narrow it to the bookings it is actually for.
To stop a rule firing for one property, add that property to the rule’s exclude list. To stop it firing for a whole channel, a length of stay, a party size or a booking made at short notice, use the matching condition below. Every condition is optional and every one of them only ever narrows.
-
Open Automation → Agent Hub. For a built-in, press Set up (or edit a property’s row) on its card on the Built-in tab. For an automation you wrote, press Edit on its card on Your automations.
-
Open its conditions. On a built-in’s settings sheet they sit under Which bookings; on your own automation, under Only for some bookings on the Review step. Only the automations that resolve one booking per message offer them - see the note below.
-
Set what you need. Everything is optional.
-
Save, then watch the run history to see what fired and what was filtered out.
What you can filter on
Section titled “What you can filter on”| Condition | What it means |
|---|---|
| Skip these properties | An exclude list. Leave every property unpicked and it runs for all of them; a property you add next month is included automatically. |
| Booking channel | Fire only for these channels: Airbnb, Booking.com, Expedia, Agoda, Vrbo, Direct or Offline. Pick none to run for every channel. |
| How far ahead it was booked | Any, Same day, or At least… a number of days ahead, counted in whole days from the booking being made to the arrival date. |
| Length of stay | Any, One night, or 2 or more. |
| Guests, at least / Guests, at most | The party size, inclusive at both ends. |
| Returning guest | Any, Returning, or First-time. |
| Identity verified | Any, Verified (every identity check on the booking has passed), or Not verified. |
| Free nights after, at least / at most | The gap before the next arrival on the same unit. 0 is a same-day turnover; a stay with nothing booked after it matches neither bound. Useful for “offer a late checkout when nothing follows”. |
Adding conditions never widens a rule
Section titled “Adding conditions never widens a rule”Conditions are only ever a narrowing. There is no combination that makes a rule fire where it did not before, and an empty set matches everything - so a rule that has been running untouched keeps running exactly as it did.
When a rule goes quiet
Section titled “When a rule goes quiet”A booking that a condition leaves out produces no run at all: the automation simply did not apply to it, so the run history shows nothing for that booking. If an automation that used to send has gone quiet, open its conditions first.