> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/integrations-overview/setup-tripleseat.md). # How to Set Up TripleSeat > **Walkthrough (Peoplevine × TripleSeat):** [Watch here](https://www.loom.com/share/e050553d8fa74812b98f8caf49889fbb) ### Before you begin (Prerequisites) * **Permissions**: You must be an **Administrator** or **Supervisor**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). * **TripleSeat account** with API access enabled, and a **TripleSeat login that can authorize the connection** (new connections use OAuth 2.0). * **Credentials from TripleSeat**: Consumer Key (or Consumer Token), Consumer Secret, Site ID, and Account ID. Find these in TripleSeat under **Settings > Tripleseat API & Webhook details**, or contact your TripleSeat representative. * **Recommended:** Create a dedicated TripleSeat account named `Peoplevine` to use as the Account ID for this integration. > For full setup instructions including TripleSeat-side configuration, credential lookup steps, and screenshots, see [Connect TripleSeat and Peoplevine](https://docs.peoplevine.com/peoplevine-docs/peoplevine-connect) in Peoplevine Connect. The steps below cover the Peoplevine Control Panel side. ### Instructions 1. Navigate to [**AUTOMATE > Integrated Platforms**](https://control.peoplevine.com/admin_authenticate.aspx). > **Note (Pro Dash):** Same path — **AUTOMATE > Integrated Platforms**. 2. In the **Reservations** section, select **Tripleseat**. 3. Choose the environment you want to connect to. 4. Enter your **Consumer Key** (or **Consumer Token**) and **Consumer Secret**. 5. Enter your **Site ID**. > To find the Site ID yourself: in TripleSeat, go to **Settings > Tripleseat API & Webhook details > Tripleseat Public API key**, click **rooms and locations**, and locate `site_id` on the first line. Use only the numeric value. 6. Enter your **Account ID**. > Recommended: create a dedicated account in TripleSeat named `Peoplevine` and copy the Account ID from the URL after creating it. 7. Select the **event statuses** you want to sync into Peoplevine. Recommended: **Definite** and **Closed**. 8. (Optional) Enable **Order Sync From Tripleseat** if you want events to appear as orders for revenue reporting. > **Warning:** Order sync can create duplicates if you also enter orders manually in your POS. Leave it off if you only want events to appear as bookings on the member calendar. 9. Click **CONNECT**. 10. **Authenticate the connection** — new connections use **OAuth 2.0**. After the configuration is created, the page returns to your TripleSeat locations list; click **Authenticate** to complete the authorization (you'll need a TripleSeat login that can authorize the connection). 11. Use the **Sync** option to pull initial members and reservations. After that, the integration syncs automatically. ### What Gets Synced | Data | Direction | Timing | | ------------------------------ | ------------------------- | ----------------------------------------- | | Member profiles (name, status) | Peoplevine --> TripleSeat | On enrollment + updates | | Membership status changes | Peoplevine --> TripleSeat | Real-time | | Event reservations | TripleSeat --> Peoplevine | Real-time (filtered by selected statuses) | | Events as orders (optional) | TripleSeat --> Peoplevine | On sync (if order sync enabled) | > **Not supported:** Availability lookup, booking, and cancellation from the Member Portal are not currently supported for TripleSeat. ### Best Practice * **Start with Definite and Closed statuses only** — syncing Prospect or Tentative events can create noise in your member calendars. Add more statuses after you confirm the integration is working. * **Create a dedicated TripleSeat account** — using a shared account makes it harder to audit which changes came from the integration vs. manual edits. * **Leave order sync off unless you need revenue reporting** — if your POS already captures event revenue, enabling order sync creates duplicate order records in Peoplevine. * **Use the initial Sync after connecting** — the automatic sync only picks up new activity. Run the initial sync to pull existing reservations and member data. ### Common Issues **Consumer Key or Secret rejected:** In TripleSeat, go to **Settings > Tripleseat API & Webhook details**, enter a technical contact email, and TripleSeat will email fresh credentials. Use these instead of any previously shared values. **Events not appearing in Peoplevine:** Check which event statuses you selected during setup. Only events matching the selected statuses sync. If you only chose **Definite** and the event is still marked **Tentative** in TripleSeat, it will not appear until the status changes. **Duplicate orders in Peoplevine:** This happens when **Order Sync From Tripleseat** is enabled and orders are also entered manually in a POS. Disable order sync if you do not need it for revenue reporting. **Site ID not working:** Ensure you are using only the numeric value from the `site_id` field, not the full API key string. See the Site ID lookup steps in Instructions above. ### What Happens Next * Synced events appear as appointments in the Peoplevine Control Panel * Members see their TripleSeat reservations on the member calendar in the Member Portal and Member App * Membership status changes in Peoplevine update TripleSeat automatically, so event staff always see current member tier * Peoplevine creates schedulers automatically based on your TripleSeat configuration *Last updated: 2026-05-24* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/integrations-overview/setup-tripleseat.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.