Triggers
Every trigger carries the reservation’s code, guest name and email, experience, venue, location, party size, date, time, channel, and whether the guest is a member — so your conditions can be as specific as you like.Actions
Good to know Triggers appear in Flow’s editor shortly after installing or updating Riserva. A workflow that fails on Flow’s side never affects the reservation itself — automation failures are recorded on the reservation’s timeline instead. Reservation created fires for online orders and for reservations made in the Riserva admin. Booking a reservation on the POS register, or seating a waitlist party from the register, doesn’t fire it. Checking a party in or marking a no-show on the register does fire Guest checked in and Reservation no-show.What things mean on this screen: What things mean: Settings
Related
- Klaviyo — the same reservation moments as marketing events