> ## Documentation Index
> Fetch the complete documentation index at: https://docs.riservahq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Shopify Flow — automate around reservations

*New*

Riserva plugs its reservation moments into **Shopify Flow**, Shopify's free
automation platform: pick a trigger, add conditions, choose actions — no
code. There is nothing to configure in Riserva; the triggers appear in
Flow's editor automatically, under Riserva's name.
**Settings → Integrations → Shopify Flow** explains the surface in-app, and
its **Open Shopify Flow** button takes you straight there — or, if Flow
isn't installed yet, Shopify offers it to you on the spot (it's free).

***

## 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.

| Trigger | Fires when | For example |
| - | - | - |
| **Reservation created** | A reservation is booked — an online order, **Book reservation** in the admin, or a waitlist party seated from the admin's Host view | Tag first-time guests; Slack the tasting room for parties of 8+ |
| **Reservation cancelled** | Cancelled by the guest or by staff | Start a win-back flow; alert the host when a same-day table frees up |
| **Guest checked in** | The party arrives and is checked in | Award loyalty points; schedule the next-morning thank-you |
| **Reservation no-show** | Marked a no-show — by staff, or by the automatic rule under Settings → Reservations → No-shows | Tag repeat no-shows; send a gentle rebooking nudge |

## Actions

| Action | What it does |
| - | - |
| **Add note to reservation** | Writes a note onto the reservation's timeline by its reservation code — e.g. "VIP: third visit this quarter", decided by your own workflow conditions |

***

> **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](/reference/settings)

## Related

* [Klaviyo](/integrations/klaviyo) — the same reservation moments as marketing events


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.