Upfirst is an AI receptionist that connects to Jobber in two ways: through Custom Actions (live GraphQL API calls during a call) and through Zapier (writes to Jobber after the call ends). Every inbound call ends up tied to the right Jobber client, request, or job.

Does Upfirst integrate with Jobber?

Yes. Two options:

• Custom Actions let your receptionist run live GraphQL queries against Jobber during a call. Find a client by phone, check a quote, look at a job's status. The receptionist uses the answer on the call.
• Zapier handles the post-call work. Turn a completed call into a new client, a request, a quote, or a note.

Most shops with a busy phone line run both. Custom Actions while the call is happening, Zapier for the catch-all logging afterward.

What Jobber is

Jobber is field service management software for home service businesses. The core objects are Clients, Properties, Requests (inbound leads), Quotes, Jobs, and Invoices. Plumbers, electricians, landscapers, cleaners, and lawn care companies use it to run scheduling, dispatch, and invoicing without spreadsheets.

Inbound calls feed the front of the Jobber pipeline. The integration with Upfirst makes sure no caller falls out before they hit the Request queue.

What Upfirst can do with Jobber

Recognize existing clients on the first ring

When a call comes in, Upfirst queries the Jobber clients connection by the caller's phone. If there's a match, the receptionist greets them by first name and can reference the property on file, an open quote, or the last job they had done.

Repeat clients hear "Hi Sarah, are you calling about the lawn service at the Maple property?" instead of "Can I get your name?"

Check a quote, job, or request status mid-call

When a caller wants to know if their crew is on the way, what their quote totals, or whether their invoice is paid, the receptionist asks for the address, job number, or name, queries Jobber on the spot, and reads back what it finds. Any field on a Client, Request, Quote, Job, or Invoice node is fair game, including your custom fields.

Drop new leads into Jobber as Requests

When the call ends with a new lead, Upfirst runs a requestCreate mutation. The Request lands in the office's intake queue with the caller's contact info, the service they need, the property address, and the call transcript as a note. Dispatch picks it up like any other Request.

Filter calls by service area or trade before they land

Upfirst can pull anything you want out of a call: zip code, service type, urgency. Use those signals to skip the Request creation if the caller is out of your service area, or tag it "same-day" when they say it's an emergency. Jobs you can't do stay logged but don't clutter the dispatch board.

Jobber API calls Upfirst can make

• Query clients by phone, name, email, or address
• Query requests, quotes, jobs, or invoices by id or by client
• Run clientCreate or clientUpdate with custom fields
• Run requestCreate to push a lead into Jobber's intake queue
• Run quoteCreate tied to a Client and Property
• Run noteCreate to attach the call summary to a Client, Request, or Job

Setting up the Jobber integration

Custom Actions

1. In the Jobber Developer Center (developer.getjobber.com), register an app and complete OAuth setup. Save the Client ID and Client Secret. Add a redirect URI for Upfirst.
2. In Upfirst, set up the Jobber OAuth Connection. Then go to Agent > Custom actions and add a new action.
3. Pick when it runs: When call starts for the client lookup by phone, During call for status checks the caller asks about, or After call for Request creation.
4. Set the request. Method POST. Endpoint https://api.getjobber.com/api/graphql. Put your GraphQL query or mutation in the body. Reference #{{caller_id}} and any variables you've defined.
5. Pick the fields the receptionist gets back. Run a test. Save.

Zapier

1. Create a Zap. Trigger: Upfirst > Call Completed.
2. Pick a Jobber action: Create Client, Create Request, Add Note.
3. Map the call fields to Jobber fields. Service, property address, and notes are the ones that matter.
4. Add filters if you only want certain call types to create Jobber records.
5. Test with a real call. Turn the Zap on.

For most shops the right starting point is a client lookup on call start and a Zapier workflow for Request creation on call end. Add mid-call GraphQL queries as the office finds use for them.