# Jobber integrations: clients, jobs and quotes

> Create a client, create a job and create a quote in Jobber, and start a workflow when Jobber sends “Client created”.

**Canonical page:** https://tray.ai/connectors/jobber-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Jobber is field service software for home service businesses, covering client records, quotes, job scheduling, invoicing and payments. Tray.ai connects to Jobber through the HTTP Connector, so your workflows can call the Jobber API alongside the rest of your stack. API access comes through Jobber's partner program or API plan, so you need approved credentials first.

## Use cases

### Clients

Read, create, and update clients in Jobber from any Tray.ai workflow. The Jobber API covers calls such as list clients and create a client.

- List clients
- Create a client
- Edit a client

### Jobs

Read, create, and update jobs in Jobber from any Tray.ai workflow. The Jobber API covers calls such as list jobs and create a job.

- List jobs
- Create a job
- Edit a job

### Quotes

Create and update quotes in Jobber from any Tray.ai workflow. The Jobber API covers calls such as create a quote and edit a quote.

- Create a quote
- Edit a quote

### Invoices

Create and update invoices in Jobber from any Tray.ai workflow. The Jobber API covers calls such as edit an invoice and add an invoice note.

- Edit an invoice
- Add an invoice note

### Jobber events

Start a Tray.ai workflow the moment something happens in Jobber. Jobber sends events such as client created and invoice updated to a Tray.ai webhook trigger.

- Client created
- Invoice updated
- App connected

## Challenges Tray.ai solves

### Keeping Jobber credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Jobber credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Jobber API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Jobber API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Jobber?

Yes. Tray.ai connects to Jobber through the HTTP Connector, which calls the Jobber API directly. Any call the Jobber API documents can run as a step in a Tray.ai workflow. API access comes through Jobber's partner program or API plan, so you need approved credentials first.

### How does Tray.ai authenticate with Jobber?

The Jobber API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Jobber connector?

Jobber runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Jobber connector from the Jobber API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/