Integrations
Connect the tools your shop already runs on.
I got tired of re-typing every paid invoice into the books and every booking into a second calendar. So Service VIN connects to the payment, accounting and scheduling tools you already run — quotes, jobs, invoices and film cost move between them without a copy-paste. Here are the deep, dedicated connections.
Looking for something else?
Payments, accounting, calendars, automation, texting, reviews and film-supplier catalogs — 6 connectors are live, with more in beta and on the roadmap. Browse them all, or request the one you need.
Why bother connecting
What connecting actually saves you
Three jobs that stop being jobs. Each row names the connector that does it and carries its real status from the registry — not a claim about how many shops use it.
- ●QuickBooks Online · Beta
Month-end stops being a data-entry night
Paid invoices, taxes and payouts post into your books as they happen, matched to the customer and the job they came from — instead of an export, a spreadsheet and an evening of matching rows.
- ●Google Calendar · Beta
Your two calendars stop disagreeing
Bookings and bay assignments sync with the calendar your phone already shows you, so a job that moves in one place has moved in both — and nobody double-books a bay from the wrong screen.
- ●Stripe · Connected-ready
A payment is a payment, not a reconciliation
Card payments, deposits and refunds land against the invoice and the job on their own. There is no second system holding the truth about what a customer has actually paid you.
Integrations, answered
Which plan includes integrations?
Growth and up — the connector hub, the OAuth handshake and the per-shop token vault all sit behind that gate. The 14-day free trial includes everything, so you can connect your real accounts and watch a real payment or booking flow through before you pick a plan. Platform-level connections that need no setup at all (payments processing, texting, the verified email sender) are on from the moment your shop exists, on every plan.
What does a status badge actually mean?
Exactly what it says, and we would rather say the unflattering version. "Connected-ready" means the adapter ships and works today. "Beta" means it is usable with rough edges and you opt in. "Coming soon" means we are actively building it — scoping or provider approval is in flight. "On the roadmap" means it is on the roadmap and not started, and the button registers your demand instead of pretending to connect. Every badge on this page is read from the same registry the product reads.
Which way does the data move?
It depends on the connector, and each one says so on its own page rather than leaving you to find out. Some are one-way into Service VIN (a lead source), some are one-way out (invoice export), and some are kept in sync both directions. Connecting an account is never destructive by itself: an OAuth connection is scoped to what the integration needs, and where a connector only reads — the Google Ads audit, for instance — connecting changes nothing in your account.
What if the tool I use isn't here?
Tell us and it gets counted. The full directory has a request form on every connector that isn't built yet, and demand is genuinely how the order gets decided. In the meantime two paths usually cover it: a webhook can POST a signed payload to any URL you control on every meaningful event, and if the tool is something you are leaving rather than keeping, a CSV export is all our concierge migration needs.
Stop re-typing the same invoice twice.
Connecting is read-and-write where you allow it and read-only where you don't, it takes a few minutes, and the free trial includes every connector on this page — so you can see a real payment land in your books before you decide anything.