Webhooks
Every shop event, POSTed to a URL you control.
This is the piece everything else in the automation category sits on. Quote sent, job won, invoice paid, call missed — each one can POST a signed payload to an endpoint you own, so whatever you've already built hears about it the moment it happens.
- Status
- Connected-ready
- Data
- Service VIN → tool
- Category
- Automation
The short answer
What does the Webhooks integration actually do?
- Where it stands: Connected-ready.
- Which way the data moves: Service VIN → tool.
- Signed, versioned event payloads
- Subscribe per event type (quote.accepted, invoice.paid, …)
- Retries with backoff + a delivery log
Bottom line: Webhooks are live: the endpoints, the signing, the per-event subscriptions, the retries and the delivery log all ship today. There's no third-party account to authorize — you add a URL and pick the events.
Why connect Webhooks
Fire a signed webhook on any shop event.
Every meaningful event — quote sent, job won, invoice paid — can POST a signed payload to a URL you control. The building block the whole automation category sits on.
Signed and versioned payloads
Every delivery carries a signature you verify and a version you can pin against, so your endpoint can trust what it just received and doesn't break the week a field is added.
Subscribe per event, not to everything
Pick the events you care about — quote.accepted, invoice.paid, job.stage_changed — instead of filtering a firehose on your side.
Retries with backoff, and a log
A delivery that fails is retried with backoff, and every attempt is written to a delivery log you can open. An integration that fails quietly is worse than one that doesn't exist.
The floor Zapier and Make stand on
The no-code tools in this category are built on this rail. If you'd rather write the handler yourself, you're working from the same events they are.
What ships
What you can do once it’s connected
- 01Signed, versioned event payloads
- 02Subscribe per event type (quote.accepted, invoice.paid, …)
- 03Retries with backoff + a delivery log
- 04The foundation Zapier/Make sit on top of
How it works
Setting it up, in order
Add an endpoint
On the webhooks settings page, point Service VIN at a URL on your own server or at any tool that accepts inbound hooks. No OAuth, no third-party account.
Choose the events
Subscribe the endpoint to the event types it should hear about. The lead, quote, job, appointment, invoice, message, conversation, call, warranty and review lifecycles all publish.
Verify the signature and act
Your handler checks the signature, reads the payload and does whatever it does. Failed deliveries retry on their own and every attempt is on the log.
Setting up Webhooks, step by step: API keys & the public API (with Zapier & Make recipes).
FAQ
Webhooks, answered
Does Service VIN support webhooks?
Yes, and they're live. Every meaningful shop event can POST a signed, versioned payload to a URL you control — quote sent and accepted, job created, stage changed and completed, appointment booked, rescheduled and canceled, invoice paid, messages sent and received, calls missed and completed, warranty issued. Deliveries retry with backoff and every attempt is written to a delivery log.
Which events can I subscribe to?
Around two dozen, covering the lead, quote, job, appointment, invoice, message, conversation, call, warranty and review lifecycles. Each has a stable name — invoice.paid, job.stage_changed, call.transcript_ready — and the settings page lists them with their payloads.
How do I know a delivery is really from you?
Every payload is signed. Your endpoint verifies the signature before it acts on the body, which is what lets you expose a handler on the open internet without it being a door.
What happens when my endpoint is down?
The delivery is retried with backoff rather than dropped, and every attempt — the successes as well as the failures — is written to a delivery log you can read.
Do I need webhooks if I already use Zapier?
No. Zapier and Make sit on this rail, so a Zap already receives these events without you writing a handler. Webhooks are for the case where you'd rather own the code, or where the destination is something no no-code tool connects to.
Or start smaller
The call you missed is the job you lost.
Every missed call answered in seconds. The quote you promised, drafted before you hang up. Booked straight into your calendar.
It answers from your real services, your real prices and your real calendar — and writes the booking into them. No migration, no data to move — it runs beside whatever you use today.
Run the whole shop — Webhooks included.
Quotes, bookings, film inventory and the AI crew in one login. Connect Webhooks on the free trial and watch a real payment or a real booking move between two systems before you decide anything.
Connected-ready · Service VIN → tool