Turnhouse SystemsBook a demo

Integrations

What connects, which way the data moves, and whether it is live today. Direction matters more than the logo: an integration that only reads is a different piece of work from one that writes back.

Filter by category

  • Stripe

    Takes the payment at checkout and writes the settlement back against the booking, so a refund in the console is a refund at the provider.

    Two-wayPayments

  • Adyen

    The same contract as Stripe, for operators who already settle through Adyen. Payment methods available per location come from the tenant record.

    Two-wayPayments

  • PayPal

    Offered as a checkout option. Refunds are initiated from the console and reconciled on the provider side.

    OutboundPayments

  • Twilio

    Booking confirmations and change notices by SMS, sent from your own number rather than a shared one.

    OutboundMessaging

  • Postmark

    Transactional email for confirmations, reminders and cancellations, on your own sending domain.

    OutboundMessaging

  • WhatsApp Business

    Beta

    Confirmations out, and replies routed back to the booking they belong to. In beta: template approval is still manual.

    Two-wayMessaging

  • Google Calendar

    Staff availability read in, assigned work written out. A calendar block created here appears against the right person in the console.

    Two-wayCalendars

  • Microsoft Outlook

    The same two-way contract as Google Calendar, for teams on Microsoft 365.

    Two-wayCalendars

  • iCal feed

    A read-only feed per location, for anyone who needs the schedule in a calendar you do not manage.

    OutboundCalendars

  • Xero

    Daily settlement summaries pushed as draft invoices, split per location so each one reconciles on its own.

    OutboundAccounting

  • QuickBooks

    The same daily push as Xero, mapped to your own account codes.

    OutboundAccounting

  • Okta

    Single sign-on for console accounts. Roles map from directory groups, so an offboarded staff member loses access when the directory says so.

    InboundIdentity

  • Microsoft Entra ID

    SAML single sign-on for console accounts, with the same group-to-role mapping as Okta.

    InboundIdentity

  • SCIM provisioning

    Beta

    Accounts created and deactivated from your directory rather than by hand. In beta: group scoping to a single location is not covered yet.

    InboundIdentity

No integration matches this filter.

Not on the list?

The API accepts the same records the console writes, so anything the console can do can be done from your own code.

Read the API documentation

See it with your own inventory in it.

A demo runs on your services and your pricing, not on a sample account. Thirty minutes, and you keep the setup.

Book a demo