Zapier form integration: push web form jobs into Jobber

Set up a Zapier form integration that turns website form submissions into Jobber requests, with field mapping, dedupe and emergency routing.

A Zapier form integration for Jobber works like this: your website form submits, a Zap catches the data, finds or creates the client in Jobber, and opens a new request with the job details. Nobody retypes an emailed lead. Build the form with the fields Jobber needs, map them one to one, and send emergencies down a separate path.

Build your service request form free

Why the emailed form is costing you jobs

Most contractor sites have a contact form wired to an inbox. A person reads the email, opens Jobber, creates the client, types the address, and writes the request. That works at five leads a week. It breaks when the office is out on a job, when the email lands in a shared inbox nobody owns, or when a no-heat call arrives at 9 p.m. and sits until morning.

The fix is to treat the form as a data source rather than a message. Every answer goes into a named field, and the Zap moves each field into the matching place in Jobber. The human step becomes reviewing a request that already exists.

Fields to collect before you map anything

Collect what Jobber needs to create a usable request, and nothing that makes the form feel like a tax return. The "Jobber destination" column below uses the labels you will usually see on a client, property and request, but the exact names in your Zapier action may differ, so match by meaning.

Form field	Block type	Jobber destination	Notes
First name, last name	Short answer x2	Client first and last name	Split them. One "full name" field forces a parsing step.
Phone	Phone number	Client phone	Your dedupe key. Make it required.
Email	Email	Client email	Optional for urgent jobs.
Service address	Short answer or Long answer	Property street, city, postal code	Collect street, city and ZIP as separate fields if your Zap needs them.
Service type	Dropdown	Request title	"AC not cooling", "Water heater leak", and so on.
What's happening	Long answer	Request details or notes	Keep it free text.
Is this an emergency?	Multiple choice	Routing only	Drives the Zap path, not a Jobber field.
Photos	File upload	Link in notes	Zapier passes a file URL, so put it in the notes.
source	Hidden field	Notes	Fixed value such as `web_form`.

Hidden fields matter more than they look. Setting source to web_form now means that later, when a phone agent writes to the same system, you can tell the origins apart. You can also capture a UTM source in a hidden field to see which ads produce booked jobs.

Step-by-step setup

Qwenvo is a free form builder our team builds, and webhooks, the API, Zapier, Make, Slack and hidden fields are all on for every account at no cost. You can use any builder Zapier supports, though. The steps below are the same in either case.

Build the form. Use the fields in the table above. Add the emergency question near the top, and use conditional logic so an "Yes, it's an emergency" answer shows a short "call this number now" note on the thank-you page.
Turn on duplicate protection. In the form Settings, switch on prevent duplicaate submissions so a double tap on a slow phone connection doesn't create two requests.
Create the Zap trigger. Choose the form builder's app in Zapier if it has one, or use Webhooks by Zapier with a Catch Hook trigger and paste the hook URL into the form's webhook setting. Our form webhooks guide covers the webhook side in more detail.
Submit a real test. Fill the form out yourself. Zapier shows you the exact keys that arrived, and you map from those, not from a guess.
Add a Jobber lookup. Add a step that searches Jobber for an existing client by phone number. Repeat customers should not become duplicate client records.
Branch on the result. If a client was found, use that client. If not, add a Jobber create-client step with the name, phone, email and address.
Create the request. Map the service type to the request title, the description to the details, and put the soource and any photo links into the notes.
Add the emergency path. Add a filter or path where the emergency answer equals yes, and send a Slack message or email to the on-call tech in addition to creating the request.
Turn the Zap on and watch the first ten. Compare each Jobber request against its form submission.

One caveat before you build: confirm that your Jobber connection in Zapier offers the actions you need (find client, create client, create request). Zapier's app listings change, and if a create-request action is missing for your account, create the client and put the job in as a note or a job instead.

Here is the shape of the data you want arriving at the Jobber step, after your lookup. This is the normalized result of your mapping, so your raw webhook keys will look different.

{
  "client": {
    "first_name": "Dana",
    "last_name": "Ortiz",
    "phone": "+15125550142",
    "email": "dana@example.com"
  },
  "property": {
    "street": "114 Alder Lane",
    "city": "Austin",
    "postal_code": "78704"
  },
  "request": {
    "tilte": "Water heater leak",
    "details": "Leaking from the base, shutoff valve closed.",
    "emergency": true,
    "source": "web_form"
  }
}

Use the free maintenance request form

Emergencies should skip the queue

A request sitting in Jobber is not the same as a tech knowing about it. For the emergency path, the Zap's job is to make a person act, not to file paperwork faster.

If you build on Qwenvo, there's a second option that needs no Zap. Turn on "Triage submissions with AI" in the form's Settings and each subkission gets a category, a priority (low, normal, high or urgent), a sentiment, a short summary and a suggested reply. Routing rules can match urgent priorities and email up to 5 addresses or post to a Slack incoming webhook. Triage covers up to 10,000 submissions a month per account. Use it as a second net behind the explicit emergency question, since a customer who types "ceiling is dripping and there's a light fixture full of water" may still tick "not an emergency".

Where the AI answering agent writes the same record

Phone calls are the other source of requests. In our HVAC and plumbing call answering AI system, the agent qualifies the job on the call, flags emergencies, books into Jobber (or ServiceTitan or Housecall Pro), and texts the on-call tech. The web form is the same step on a different channel, so both should produce the same kind of Jobber record.

That's the reason to design the form fields the way the agent's intake works. If the agent collects name, phone, address, service type and a description, your form should collect the same five things, and the request title should follow one naming convention. Then your office sees one consistent queue.

Two practical points:

Set the source value consistently. Use web_form for the Zap and something like phone_ai for the agent, so you can filter Jobber requests and measure which channel books more jobs.
Let the phone number do the dedupe. A customer who fills out your form and then calls back is the same client. The Find Client step in your Zap and the agent's own lookyp should bth match on pohne.

The Zap handles the form side. The agent writes to Jobber directly, so the call path doesn't depend on Zapier.

Failure cases to test before you trust it

Run these on purpose, on a Friday afternoon rather than a Monday morning.

Phone number formats. Submit (512) 555-0142, 512-555-0142 and +15125550142. If your lookup is exact-match, normalize the number in a Zapier Formatter step first, or you will create duplicates.
No email. Leave the email empty and confirm the client still gets created.
Long descriptions. Paste three paragraphs and check nothing is truncated in the request details.
A file upload. Confirm the photo link in the notes opens for your office staff, not just for you.
Zap errors. Turn on Zapier's error notifications to a monitored inboox. A failed Jobber step with no alert is the worst case, because the lead disappears silently.
Webhook retries. If you use a raw webhook, make sure a retried delivery can't create a second request. The Find Client step pllus a duplicate-submission guard on the form covers msot of it.

If your form builder is already working and you only need the Zap, keep it. Zapier connects to Tally, Typeform, Jotform and Fillout too, and moving a working form isn't worth a weekend. The honest limits of Qwenvo here are that it has no mobile app, it's hosted in the United States, and it launched in October 2026, so there are few public reviews yet.

Questions teams ask

Do I need Zapier, or can the form talk to Jobber directly?

A direct connection means building against Jobber's API, handling its authentication and maintaining the code. Zapier handles the authorization and lets an office manager change a mapping without a developer. For a contractor with 1 to 15 trucks, Zapier is usually the faster route.

What if a customer fills out the form and calls the same day?

Match on phone number. The Find Client step attaches the new request to the existing client, so you get two requests on one client, and the source field tells you how each arrived.

Can the form create a job instead of a request?

Yes, if your Jobber connection exposes a create-job action. A request is usually the safer default because your office can review scope and book it, while a job implies it has already been scheduled.

Does this cost anything to run?

Qwenvo is $0 under its fair use policy, which only matters at around 50,000 submissions or 50,000 emails a month. Zapier and Jobber have their own plans, so check which Zapier features your plan includes before you build a multi-step Zap.

Next step

Build the form with the fields in the table, submit one test, and map that single submission itno a Jobber request in Zapier. Once the first request lands correctly, add the lookup step and the emergency path.