Integrations

Integrations for Booking Automation

Connect OnsitePilot to Google Calendar, Square, and TomTom to bring real-world context into your booking workflow.

Current public integration count: 3
Current connected systems: Google Calendar, Square, TomTom
Each integration supports a specific booking decision, not generic connector sprawl

Current integration surfaces

3 pages
Calendar Sync

Google Calendar Integration for Confirmed Booking Sync

The Google Calendar integration keeps confirmed booking changes mirrored into the operator's calendar during the current beta.

What It Does

Confirmed, rescheduled, and cancelled bookings can sync to the provider’s Google Calendar.

Current Boundary

Current build is write-only sync. Busy-read is not part of the booking truth in the current public scope.

  • Write confirmed booking changes into Google Calendar.
  • Reduce double work between booking conversations and the real day plan.
  • Keep scheduling decisions closer to actual operator availability.
Read integration details
Deposits

Square Integration for Deposit Confirmation and Booking Flow Control

The Square integration supports OnsitePilot deposit confirmation flow so solo service businesses can connect payment intent to whether a slot stays protected.

What It Does

Deposits go to the provider’s own Square account through hosted Square checkout.

Current Boundary

Square is used for payment state, not as the booking system of record.

  • Connect deposit confirmation to booking progression.
  • Keep money inside the operator's own Square account flow.
  • Reduce manual checking before a booking becomes trustworthy.
Read integration details
Routing

TomTom Integration for Route-Aware Booking Checks

The TomTom integration supports route-aware booking logic so solo service businesses can evaluate travel feasibility before confirming appointment times.

What It Does

TomTom supports address search and route-aware ETA checks for slot feasibility.

Current Boundary

Current map and routing supplier is unified to TomTom, not multiple map providers in parallel.

  • Bring travel context into slot evaluation.
  • Reduce impossible arrivals created by flat calendar logic.
  • Support cleaner same-day and reschedule decisions.
Read integration details

Why these integrations exist

The goal is not to accumulate connectors. Each integration exists because it changes a booking decision: calendar context changes whether a slot is workable, route context changes whether it is physically reachable, and payment state changes whether the slot deserves protected time.

What this hub does not claim

  • It does not claim a generic integration marketplace.
  • It does not claim current support for Outlook, Apple Calendar, or alternative map providers.
  • It does not claim that third-party tools replace OnsitePilot as the booking decision engine.