Integrations
Works with what you use
METBooker connects to your payment provider, your calendar, UK vehicle data and your email, and exports to your bookkeeping software, so details are typed in once, on the booking.
What connects
Each connection, what it does in METBooker, and where it is described in more depth.
| Area | Connects to | What it does |
|---|---|---|
| Card payments | Stripe, SumUp, Square or Dojo | Deposits and payments through the provider's checkout into your own account; Stripe card reader at the counter. Payments |
| Calendars | Google Calendar, Microsoft 365 | Each booking written to the right person's calendar, and their busy times checked before a slot is offered. Staff can use METBooker's own calendar instead. |
| Vehicle data | DVLA and DVSA data | Vehicle details from the registration and full MOT history. Vehicles |
| Travel time | Google Maps | Journey times with traffic for mobile work, and address suggestions as customers type. |
| Gmail, Microsoft 365 | Customer emails from your own address, or from METBooker's sender. | |
| Bookkeeping | Export files for Xero, QuickBooks, Sage and others | Invoices, payments and refunds by VAT quarter or tax year. Invoicing |
| Measurement | Google Analytics 4 | A completed booking recorded as a conversion in your own Analytics property. |
| Monitoring | UptimeRobot | METBooker's services are monitored, with the status shown in your admin console. |
Where data lives
METBooker's application database is hosted by Google Cloud in London. Payment providers, email services and the other services above handle the data they need under their own terms, listed in the data processing agreement. Card details are entered on the payment provider's checkout and never pass through METBooker.
Connections in use
Where next
Integrations support the platform. The platform itself is explained area by area.