OpenTable reservations can now trigger Klaviyo flows in real time

Hey restaurant folks,

A guest books a table for Saturday. Your reservation team knows. Your floor team knows. And now your marketing can know in real time, too.

The updated OpenTable integration brings reservation activity and guest details into Klaviyo as they happen. If your restaurant's POS is connected to OpenTable, order details can come through as well. That gives restaurant marketers a much clearer view of who booked, what changed, and what happened during the visit.

What changed

• Reservation statuses including Created, Confirmed, Cancelled, No Showed, and Completed arrive in Klaviyo when they change in OpenTable.

• Each booking lives on the guest profile as a Reservation object, with details such as party size, scheduled time, table category, visit tags, booking origin, special requests, and location.

• You can build a date-triggered flow around the reservation's scheduled time, segment guests with upcoming bookings, and use reservation details in message content.

• When a POS such as Toast or Square is connected to OpenTable, Placed Order and Ordered Product events can include items, modifiers, and check totals.

• Historical guests, reservations, and connected POS orders are imported so you can start building segments and flows with existing data.

This is the kind of connected data that makes restaurant marketing feel less like broadcasting and more like recognizing the person who just booked a table.

Four flows worth building first

1. Pre-visit countdown: Send practical details a week before the reservation, then a shorter day-of note with the correct location, party size, parking information, or menu highlights. OpenTable already handles confirmations and reminders, so use this flow for the marketing moments around the booking.

2. Cancellation or no-show recovery: Trigger a message when the reservation status changes to Cancelled or No Showed, include a rebooking link, and use flow filters to stop follow-up messages when someone books again.

3. Spend-based VIP recognition: If POS data is flowing through OpenTable, build a VIP segment based on actual spend and invite those guests to an early tasting, chef's table, or other experience that fits your program. For more complex paths by spend, location, or visit history, multi-branch splits can keep the logic readable if they're available in your account.

4. Dish-level follow-up: After a Completed reservation, thank the guest and recommend a dish or pairing based on what they ordered. This is also a good place to coordinate email and SMS so the channels support the same guest journey instead of repeating each other.

Birthday and anniversary dates from OpenTable can support celebration outreach, too. The useful bit isn't simply having more data. It's having segmentation and flow triggers that can react to a guest's actual plans.

A few setup notes before you build

• New users can install the OpenTable app, sign in with OAuth, and choose which restaurant locations to sync.

• Existing OpenTable and Klaviyo customers need to reconnect their OpenTable account to enable the updated features, including the Reservation object.

• POS order data requires the restaurant's POS to be connected to OpenTable.

• Before setting a flow live, test the reservation statuses, location rules, dynamic reservation details, and rebooking exits you plan to use.

The updated integration is available to Klaviyo customers who use OpenTable.