What’s supported
Supported actions
This connector supports:- Read Actions, including full historic backfill. Please note that incremental read is supported for the following objects:
capitalLoans,clients,expenses,invoices,jobs,payoutRecords,quotes,requests,tasks,timeSheetEntries, andvisits. For all other objects, a full read of the Jobber instance will be done for each scheduled read. - Write Actions.
- Subscribe Actions. Ampersand creates and manages the Jobber webhook subscriptions on your behalf when the customer installs your integration — no manual webhook setup is required in the Jobber UI.
- Proxy Actions, using the base URL
https://api.getjobber.com/api/graphql.
Supported Objects
The Jobber connector supports the following objects:| Object | Read | Write | Subscribe |
|---|
For detailed information about available objects, refer to the Jobber Developer Documentation.
The full list of read and write objects can be retrieved after logging in. To explore them, go to “Manage Apps”, click “Actions” from the respective app, and then click “Test in GraphiQL”.
Subscribe events
All 12 subscribe-enabled objects in the table above support create, update, and delete events, with one exception:users has no delete event.
Please note that:
- Watched fields are not supported. Jobber webhook payloads do not include changed-field data, so field-level update filtering (
requiredWatchFields) is not available. UsewatchFieldsAuto: allfor update events — they will fire on any change to the record. - Scopes gate event delivery. Jobber only delivers events for an object if your Jobber app holds the matching read scope (e.g.
read_clientsfor client events). Make sure the scopes selected when creating your Jobber app cover every object you subscribe to.
otherEvents:
For example:
PAYMENT_CREATE, PAYMENT_UPDATE, PAYMENT_DESTROY, APP_CONNECT, APP_DISCONNECT, ON_MY_WAY_TRACKING_LINK_REQUEST, and MARKETING_ITEM_UPDATE. These can be added to the otherEvents list of any subscribed object.
Example integration
For an example manifest file of an Jobber integration, visit our samples repo on Github.Before you get started
To connect Jobber with Ampersand, you will need a Jobber Account. Once your account is created, you’ll need to Create a Jobber Developer Account and obtain the following credentials from your Jobber App:- Client ID
- Client Secret
Jobber uses GraphQL for all API operations. When making proxy calls, you must include the
X-JOBBER-GRAPHQL-VERSION header with the API version (e.g., 2025-01-20) in all requests, as this is mandatory for Jobber’s GraphQL API. You can find the latest API version information in the Jobber API Changelog.Create a Jobber developer account
Here’s how you can sign up for a Jobber account:- Go to the Jobber Developer Center and create a developer account.
- Complete the registration process and verify your email.
Creating a Jobber app
Once your Jobber Developer account is ready, you need to create a Jobber application:- Log in to your Jobber Developer Center.
- Navigate to the Apps page.
- Click NEW to create your first app.
-
Fill in the required information:
- App name (required)
- Developer name (required)
- OAuth Callback URL: Use
https://api.withampersand.com/callbacks/v1/oauth - App description (required)
- Scopes (required) - Select the data access permissions your app needs
- Click Save to create your app.
Add your Jobber app info to Ampersand
- Log in to your Ampersand Dashboard.
- Select the project where you want to create a Help Scout integration.\

- Select Provider apps.
- Select Jobber from the Provider list.
- Enter the previously obtained Client ID and Client Secret.
- Click Save changes.
Using the connector
To start integrating with Jobber:- Create a manifest file using the example.
- Deploy it using the amp CLI.
- If you are using Read Actions or Subscribe Actions, create a destination.
- Embed the InstallIntegration UI component.
- Start using the connector!
- If your integration has Read Actions or Subscribe Actions, you’ll start getting webhook messages.
- If your integration has Write Actions, you can start making API calls to our Write API.
- If your integration has Proxy Actions, you can start making Proxy API calls.

