Skip to content
Menu
Menu

Integrated solutions

Connect try.be to your wider ecosystem.

Trybe provides extension APIs and webhooks to allow for external integrations.

These can be built upon to provide for real-time or scheduled data flows between Trybe and other solutions in use across the organisation. The table below summarises some of the integrations and extensions that have been implemented for Trybe clients over the past year.

Trybe > Klaviyo EDM

Client uses Klaviyo as their source of truth for guest communication and consent. This integration uses webhooks to update Klaviyo when new guests register on Trybe, and when guests place or cancel a booking.

With additional GTM integration, the client can track the effectiveness of bulk-mail campaigns, and can segment and target their guest audience more effectively.

Trybe > Approval Max

Client uses ApprovalMax to automate the approval and lodging of purchase orders with suppliers.

This integration runs daily, and selects all new stock orders created in Trybe, and generates these in ApprovalMax thus triggering the workflow. This avoids double-handling and ‘missed’ stock orders.

TANDA > Trybe

Client uses TANDA as their People and Payroll platform.

When a new team member is created in TANDA, a webhook from TANDA triggers integration to create that person in Trybe, and to allocate them to the appropriate team.

Trybe > TANDA

Trybe provides the source of truth for session bookings with practitioners allocated. Daily, an integration process runs which calculates the ideal ‘start time’ for practitioners based on their earliest booking, and then updates TANDA to reflect this.

TANDA automatically alerts the team member of their roster start time. A summary report is produced and sent to area managers for their information.

Trybe > subtry.be (Managers Nightly)

A full schedule of ‘tomorrows’ bookings is generated and emailed to venue management. This is kept on file in the event that there is a Trybe or local communications outage, so that the venue has a record of expected guests and sessions.

Trybe > subtry.be (Reception Nightly)

A report is run to identify where large groups have made a booking (>6 PAX). The front of house team use this report to contact the lead booker to explain terms and conditions and to manage expectations and standards.

Trybe > Opera

Client is based in a multi-facility venue which includes an IHG hotel, using the Opera PMS. Using the tightly-integrated Trybe Opera adapter, the client is able to post guest sessions (i.e. bathouse, spa treatment, etc.) back to their hotel itinerary/charge, instead of taking payment over-the-counter.

The guest benefits by accruing IHG loyalty points, and there are few discrepancies between the client and the hotel management.

Trybe > Klaviyo EDM

Client uses Klaviyo as their source of truth for guest communication and consent. This integration uses webhooks to update Klaviyo when new guests register on Trybe, and when guests place or cancel a booking.

With additional GTM integration, the client can track the effectiveness of bulk-mail campaigns, and can segment and target their guest audience more effectively.

Trybe > Approval Max

Client uses ApprovalMax to automate the approval and lodging of purchase orders with suppliers.

This integration runs daily, and selects all new stock orders created in Trybe, and generates these in ApprovalMax thus triggering the workflow. This avoids double-handling and ‘missed’ stock orders.

TANDA > Trybe

Client uses TANDA as their People and Payroll platform.

When a new team member is created in TANDA, a webhook from TANDA triggers integration to create that person in Trybe, and to allocate them to the appropriate team.

Trybe > TANDA

Trybe provides the source of truth for session bookings with practitioners allocated. Daily, an integration process runs which calculates the ideal ‘start time’ for practitioners based on their earliest booking, and then updates TANDA to reflect this.

TANDA automatically alerts the team member of their roster start time. A summary report is produced and sent to area managers for their information.

Trybe > subtry.be (Managers Nightly)

A full schedule of ‘tomorrows’ bookings is generated and emailed to venue management. This is kept on file in the event that there is a Trybe or local communications outage, so that the venue has a record of expected guests and sessions.

Trybe > subtry.be (Reception Nightly)

A report is run to identify where large groups have made a booking (>6 PAX). The front of house team use this report to contact the lead booker to explain terms and conditions and to manage expectations and standards.

Trybe > Opera

Client is based in a multi-facility venue which includes an IHG hotel, using the Opera PMS. Using the tightly-integrated Trybe Opera adapter, the client is able to post guest sessions (i.e. bathouse, spa treatment, etc.) back to their hotel itinerary/charge, instead of taking payment over-the-counter.

The guest benefits by accruing IHG loyalty points, and there are few discrepancies between the client and the hotel management.