Tripleseat - Integration Set up
Rex's Tripleseat integration pushes your Rex reservations into Tripleseat as events, keeps them in sync when they change or cancel, and can pull your Tripleseat events back into Rex so they block availability. This guide covers the full setup using OAuth.
Before you start
- You'll need admin access in both Rex and Tripleseat.
- Have your Tripleseat IDs handy (Site, Owner, Event Type, Lead Source, and any custom fields). These come from your Tripleseat account.
- Tripleseat is connected once at the account level, then configured per venue, and finally your resources are mapped to Tripleseat rooms.
Step 1 — Connect Tripleseat (OAuth)
Open the Tripleseat integration card
Go to Settings > Global Integrations and open the Tripleseat card.
Enable OAuth 2.0
On the Tripleseat card, turn on Enable OAuth 2.0.
Click Login with OAuth 2.0
A Tripleseat login window opens.
Log in and authorize
Sign in to Tripleseat and authorize the connection. The window closes automatically and the card shows as connected.
To disconnect later, open the same card and click Disconnect.
Step 2 — Enter your Tripleseat IDs
On the same Tripleseat card, fill in the IDs below. All of them come from Tripleseat — your Tripleseat account manager can help if you can't find one.
| Field | Description |
|---|---|
| Site ID | Your Tripleseat site. Required to create events. |
| Owner ID | The Tripleseat user that will own the events Rex creates. |
| Event Type ID | The event type applied to events Rex creates. |
| Lead Source ID | The lead source stamped on created events. |
| Account ID (optional) | A default Tripleseat account to attach events to. |
| Contact ID (optional) | A default Tripleseat contact. |
| CF Lanes Count | A Tripleseat custom-field ID Rex uses to tag the events it creates, so it can tell them apart from events made directly in Tripleseat. |
| Reservation URL | Your Tripleseat base URL. Rex uses it to link back to pulled Tripleseat events. |
| Custom Field for Check In (optional) | A Tripleseat custom-field ID used to show check-in info on pulled events. |
| Custom Field for GoTab ID (optional) | A Tripleseat custom-field ID where Rex stores the GoTab tab ID during GoTab check-in. Only needed if you use GoTab. |
Click Save when done.
Step 3 — Turn on Tripleseat for each venue
For every venue that should sync, go to Venue Details > Venue Info > Integrations and open the Tripleseat card. Configure the fields below and save.
| Field | Description |
|---|---|
| Enable Tripleseat | Master switch for this venue. Must be on for any syncing. |
| Enable Tripleseat Party | Allow consumer party-request submissions to be pushed to Tripleseat. |
| Location ID | Select the Tripleseat location this venue maps to. |
| Room ID | Select a default/fallback Tripleseat room for the venue. |
| Timezone Offset (hours) | Hour offset applied when converting Tripleseat event times to Rex time slots. Leave at 0 unless your times come in shifted. |
| Pull events from Tripleseat | When on, Rex pulls your Tripleseat events and blocks the matching availability in Rex. |
| Statuses | Which Tripleseat event statuses count as blocking when pulling (e.g. Definite, Tentative). Only used when Pull events is on. |
| Enable Tripleseat Check In | Turn on check-in behavior for pulled events. |
| Enable Tripleseat GoTab Check In | Shown only when Check In is on. Opens and closes a GoTab tab at check-in and writes the tab ID back to Tripleseat. |
Step 4 — Map your resources to Tripleseat rooms
This tells Rex which Tripleseat room each of your resources (lanes, bays, courts, tables) corresponds to, so pulled events block the right resources and pushed events land in the right room.
Open Bulk Edit Resources
Go to Venue Details and click Bulk Edit Resources.
Choose Tripleseat and Continue
Pick the Tripleseat tile and click Continue. The Resource Mapping screen opens.
Fill out the three columns for each resource
Rex Resource is the resource name (editable). Tripleseat Room is the single Tripleseat room this resource maps to. Parent Rooms is the larger combinable rooms this room is part of — optional, see About Parent Rooms below.
Move between categories and save
Use the ‹ › arrows at the top to switch between resource categories. Click Save on each category.
To map a single resource at a time instead, open Venue Details > Resources, edit a resource, and set TripleSeat Room ID (the room) and TripleSeat Room Path (the parent rooms).
About Parent Rooms
Tripleseat lets you create combination rooms — a larger room made up of several smaller ones. When someone books the combined room in Tripleseat, the smaller rooms inside it are in use too.
Parent Rooms tells Rex about that relationship. List every larger/combined Tripleseat room that this resource's room belongs to. When Rex pulls an event from Tripleseat, it blocks this resource if the event booked either its own Tripleseat Room or any of its Parent Rooms — so a single combined-room booking correctly blocks every resource inside it.
Example: each lane maps to its own Tripleseat room (Lane 1, Lane 2, …), and Lanes 1–4 can also be booked together as "Lane Bay A." On every lane in that bay, add "Lane Bay A" as a Parent Room. Now a Lane Bay A booking in Tripleseat blocks all four lanes in Rex, not just one.
Parent Rooms only affects events pulled from Tripleseat (the Pull events from Tripleseat setting). If you don't pull events, or you don't use combination rooms, leave Parent Rooms empty.
Step 5 — Package-level settings
By default, packages use the venue's Tripleseat settings. To override them for a specific package, go to Package Details > Tripleseat and turn on Specific Tripleseat Integration. From there you can set Location, Room, Account ID, Contact ID, Event Type, Event Style, and a custom event Title for this package.
In the same modal you can map Rex reservation details to Tripleseat custom fields under Custom Fields Mapping — add a row, enter the Tripleseat Custom Field ID, and choose which reservation field should fill it (e.g. Guest Names, Group Name, Total Amount).
If you want availability for this package to come from Tripleseat instead of Rex, turn on Read availability from Tripleseat in the same panel.
Always modify events at the source. If a reservation was created in Rex, edit it in Rex — the change syncs to Tripleseat. If an event was created directly in Tripleseat, edit it in Tripleseat — Rex picks up the change on the next pull. Editing the same event in both systems will cause conflicts: the most recent sync overwrites the other side's changes.
What syncs, and when
Once setup is complete, Rex keeps Tripleseat in sync automatically. Here's what happens at each trigger:
| Field | Description |
|---|---|
| New reservation | Rex creates a matching event in Tripleseat (creating or finding the account and contact first) and links it to the reservation. Each activity on the reservation also becomes its own event. |
| Reservation changed | Rex updates the linked Tripleseat event. You can also manually re-sync a reservation from its detail page. |
| Reservation cancelled | Rex deletes the linked Tripleseat event. |
| Resources swapped | Rex updates the affected events so the rooms stay correct. |
| Party request (consumer) | When Enable Tripleseat Party is on, a party request creates an event in Tripleseat. |
| Pulling events | When Pull events from Tripleseat is on, Rex regularly pulls your Tripleseat events (filtered by the statuses you chose) and blocks the matching availability in Rex. |
| Check-in | When the check-in toggles are on, checking in a Tripleseat event can open a GoTab tab and write its ID back to the Tripleseat event. |
Good to know
- Setup order matters: connect via OAuth, enter your IDs, enable each venue, then map resources to rooms.
- If events stop syncing, re-open Settings > Global Integrations > Tripleseat. If the connection was lost you may need to click Login with OAuth 2.0 again.
Updated May 30, 2026
Was this helpful?