Integrations
Zapier, webhooks, and an honest list of what does not connect.
GuestLot connects through a Zapier app with three actions and a plain HTTP API your shop system can call directly. That covers Urable, Tint Wiz, Shop-Ware, QuoteIQ, and anything else already running Zapier — through one integration, with your vendor logins staying in your Zapier account instead of our database.
What we will not put on this page is “syncs back to your shop system”. Verified against the vendors themselves, that claim holds for about one and a half of them.
3
Zapier actions in v1
1
Active custody job per VIN
0
Vendor passwords we hold
$0
Cost of the Zapier app to you
Connects today
Three ways in, and none of them need us to build you a connector.
Every row here works now, with no partner review, no waiting list, and no per-vendor code.
- What connects today
GuestLot Zapier app
A Zapier account and a key from your Integrations screen
Start, end, and look up a custody job from any Zapier trigger — a new job in Urable, a completed job in Tint Wiz
Any webhook-capable shop system
Something in your stack that can call a URL
The same three calls the Zapier app makes, straight to /api/v1/custody/start and /api/v1/custody/end
Shopmonkey Order webhooks
A shop-admin key you create yourself in Shopmonkey
Signed events, pointed straight at us — the one source in the catalog that signs its payloads, and the record says so
Nothing at all
Nothing
The counter, the printed QR kit, and a phone. How most shops start and plenty of shops stay
Keys are minted per location under Integrations in the app. We store a hash of the key and never the key, each one shows when it was last used, and revoking is immediate.
Outbound
There is almost nothing to write back to.
We asked the question vendor by vendor instead of assuming. This is the answer.
- Write-back, by vendor
Urable
Only onto the customer record's Notes field, matched by email
The owner gets the AccessReceipt by email
Tint Wiz
A create-only message field — effectively no
The owner gets the AccessReceipt by email
Shop-Ware
No. Its actions create a repair order, customer, or appointment
The owner gets the AccessReceipt by email
Shopmonkey
Unconfirmed. We will not claim it until a live key proves it
The owner gets the AccessReceipt by email
CCC, EMS/BMS files
No. Both are read-only toward us
The owner gets the AccessReceipt by email
- The AccessReceipt goes to the owner by email — which works for 100% of shops, including the ones running no software at all.
- Anything else you want to happen at hand-back, you route in Zapier, using the shop tools you already pay for.
- We do not write the receipt into your repair order, because for most of these vendors there is no supported way to do it.
- Where a vendor does allow a note — Urable’s customer Notes, matched by email — it is a note on a customer, not on the job.
The rule that makes weak connectors safe
A connector can shorten a custody window. It can never end one.
Three of eight sources we researched have no reliable custody-end signal, so we designed as if none of them do.
When your shop system says a job is finished, GuestLot pulls the end of the custody window forward and puts a line on the board. It does not close the record, and it never pushes the end time out — extending a window means telling the owner, and that takes a person.
GuestLot’s own expiry timer stays the authoritative revoke mechanism. That way a silent vendor, a webhook a vendor disabled without redelivering, or a polling trigger fifteen minutes behind reality can never leave shop access live past the time the owner agreed to.
Every inbound event is recorded with whether it was signed, how stale it could be, and which fields it did not carry. A missing field prints as rather than a blank or a zero.
Integration event log
Coming, and what it is waiting on
Dated honestly, with the gate named.
Nothing here is bookable today. If a row matters to you, say so and it moves up.
- Roadmap, with gates
Urable through the Zapier app
Your Urable plan has to include Zapier. Whether the VIN reaches Zapier is unconfirmed — we will test it on a live account before promising VIN matching
New Job starts custody; Completed Job shortens the window
Shop-Ware through the Zapier app
Your Shop-Ware plan has to include Zapier
Repair Order Created and Updated, as Instant triggers
Mitchell and Web-Est file import
None. Both vendors document local export; Solera/Audatex refuses it, which is why it is not on this list
Collision intake from an EMS or BMS export, with no partner programme involved
CCC Secure Share
CIECA membership, a registration form, and a repairer enabling GuestLot in their own CCC settings
Collision jobs from the estimating system most shops actually run
Not building
The list we are not going to quietly leave off.
Each of these was researched and ruled out. Knowing now beats finding out during onboarding.
- Valet and parking platform APIs. Every one we looked at is sales-gated, shaped like a property-management system, and carries a monthly production fee.
- Nexsyis — confirmed to have no API. There is nothing to integrate with.
- Ceramic Pro, Identifix, Rome, and Fullbay. None of them sit between a shop and the car in a way that would tell us about custody.
- Audatex/Solera, which refuses local file export — the exact thing that makes Mitchell and Web-Est workable.
Questions
Integration questions, answered plainly.
What connects to GuestLot today?
Zapier, and anything that can call a URL. The GuestLot Zapier app ships three actions — Start Custody Job, End Custody Job, and Find Custody Job by VIN — so any tool with a Zapier trigger can open and close a custody job. Shopmonkey can post its Order webhooks to us directly, signed. And a shop with no software at all still runs the whole product from the counter, because check-in was never dependent on an integration.
Does GuestLot sync back into my shop management system?
No, and we will not say otherwise. We checked every vendor on our list: Shop-Ware's actions only create new records, Tint Wiz offers a create-only message field, Urable can write to a customer's Notes field matched by email, and CCC and EMS files are read-only toward us. That is about one and a half vendors' worth of write-back, which is not a feature. What goes out instead is the AccessReceipt, straight to the owner, plus whatever you route yourself in Zapier.
What happens when my shop system marks the job complete?
The custody window gets shorter, and nothing else. A connector's close event can only pull the end time forward — it never extends a window and never closes the record on its own. GuestLot's own expiry timer stays the thing that ends access, because three of the eight sources we researched have no reliable close signal at all: Tint Wiz sends no update events, QuoteIQ has no close semantics, and a polled source can be a full polling interval stale.
Do you store my Urable or Shopmonkey password?
No. That is the main reason we built the Zapier app before any per-vendor connector. Your vendor credentials live in your Zapier account, where you can see and revoke them, and GuestLot only ever holds a key you minted for your own location and can revoke in one click.
What does a GuestLot API key let someone do?
Start a custody job, end one, and look one up by VIN — at one location, the one that minted the key. Keys are per location, we store a hash instead of the key itself, and every key shows the date it was last used so a GM can spot one nobody remembers creating. Revoking takes effect immediately.
Will a second system starting the same car create two records?
No. One active custody job per VIN per location is enforced in the API, not by convention. A second start on a car that is already in your lot attaches its reference to the record that exists and tells the caller alreadyExisted, so a shop reading its board always sees one car once.
What are you deliberately not building?
Valet and parking APIs, which are all sales-gated with monthly production fees. Nexsyis, which has confirmed it has no API. Ceramic Pro, Identifix, Rome, Audatex/Solera, and Fullbay. Naming them saves you asking, and none of them are a reason you cannot run GuestLot tomorrow.
One key, three actions, no vendor passwords.
Open a location, mint a key under Integrations, and point Zapier at it. If your shop system cannot call a URL, the counter flow works exactly as well — it always has.