Make integration
Branching, filtered, multi-step — the shop inside Make.
Some flows are not one trigger and one action. Make reaches the same events and the same writes through Service VIN's public API and webhooks, so a scenario can branch on the value of a quote, filter out the jobs it should ignore, and do five things in order.
- Status
- Coming soon
- Data
- Two-way sync
- Category
- Automation
The short answer
What does the Make integration actually do?
- Where it stands: Coming soon.
- Which way the data moves: Two-way sync.
- Same triggers + actions as the Zapier app
- Branching, filters, and multi-step scenarios
Bottom line: Make is in beta, and it works through Service VIN's public REST API and webhook subscriptions rather than a published app in Make's directory. You mint an API key, add the HTTP and webhook modules, and the same triggers and actions the Zapier app exposes are available.
Why connect Make
Visual, branching automations.
For power users who want multi-step, branching scenarios beyond a simple trigger→action.
The same triggers and actions
The events and the writes are the ones the Zapier app uses, because they are the API and the webhook catalog underneath it — not a smaller second surface.
Branch, filter, and carry on
A scenario can route on the value of a quote, drop the events it doesn't care about, and run several steps in order. That's the reason to pick Make over a simpler builder.
A key you scope and revoke
Mint one key for the scenario, give it read-only or full access, and revoke it on its own without disturbing anything else you've connected.
What ships
What you can do once it’s connected
- 01Same triggers + actions as the Zapier app
- 02Branching, filters, and multi-step scenarios
How it works
Setting it up, in order
Mint an API key
Create a key on the API settings page, named after the scenario that will use it, with the scope it needs. Full access is required to create records or manage webhook subscriptions.
Point Make at the API
Use Make's HTTP module against the REST endpoints with the key in the authorization header. Subscribing to a webhook gives the scenario an instant trigger instead of a poll.
Build the scenario
Branch, filter, iterate. Because the surface is the API rather than a fixed app, a scenario is bounded by what the API exposes and not by what a connector's author chose to include.
Setting up Make, step by step: API keys & the public API (with Zapier & Make recipes).
FAQ
Make, answered
Does Service VIN work with Make?
Yes, in beta — through the public REST API and webhook subscriptions rather than a published Make app. You mint an API key, use Make's HTTP and webhook modules, and get the same triggers, actions and searches the Zapier app is built on.
Is there a Service VIN app in Make's directory?
Not today, and it's worth being straight about that. Make talks to the same REST API and the same signed webhook events any tool can. The connector is a documented surface rather than a listing, and the API keys page and the docs cover the endpoints and the event names.
Make or Zapier?
Zapier if the flow is one trigger and one action and you'd rather pick from a list. Make if the flow branches, filters or runs several steps in order. They reach the same events either way.
What can a scenario change in my shop?
Whatever the key's scope allows and nothing more. Read-only reads every resource and writes nothing; full access can also create leads and customers and manage webhook subscriptions. A read-only key that tries to write is refused.
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.
Quotes, bookings, film inventory and the AI crew in one login. Make is not connectable yet — everything else here is, on the free trial, before you decide anything.
Coming soon · Two-way sync