Integrations
Jobber
Connect Jobber, obtain the required access and configure permitted actions.
The API adapter is implemented. Validate your own account and authorized actions before routing production calls.
Before you start
Connect the account belonging to this business and workspace. Vendor subscriptions, API limits and role permissions still apply.
API: Jobber GraphQL API
Authentication: OAuth 2.0 access token with an active X-JOBBER-GRAPHQL-VERSION
Get access and connect
- Create a developer account and OAuth application in Jobber Developer Center.
- Configure client read/write scopes and authorize the desired Jobber account through OAuth.
- Save the authorized access token and an active API version in Verbatik. Test connection reads account id/name.
- The implemented actions read clients and jobs and create clients. Jobber exposes the full mutation schema through authenticated GraphiQL after an app and authorized test account are created; obtain that approved schema before adding job/quote mutations. They are not presented as supported here.
- Jobber access tokens expire after 60 minutes. This connection needs a fresh token after expiry; production OAuth distribution also needs refresh-token rotation and disconnect handling.
- App Marketplace review is required for broad distribution; Jobber documents custom integration limits separately.
Account requirements
- Jobber Developer Center application
- Customer OAuth authorization and current token
- An API version currently supported by Jobber
- Jobber review before connecting more accounts than its custom integration allowance
Permissions
Clients readClients writeAccount identity read
Grant the subset needed for the actions you enable. API scopes do not override the connected user’s record permissions or vendor validation rules.
Connection fields
accessToken— API key or authorized access token (required). Secret fields are saved as workspace credentials.apiVersion— Active GraphQL API version (required).
Available actions
test_connection— Read. Read account identity. GraphQL sends a POST but performs no mutation.list_clients— Read. Read 25 clients per page and the next cursor.list_jobs— Read. Read job IDs, numbers and titles from the authorized Jobber account, with bounded cursor pagination.create_client— Write. Create a client and require an empty userErrors list and a returned client ID before reporting success.
Provider-specific behavior
The current adapter reads accounts, clients and jobs and creates clients. Job and quote mutations require the customer’s authenticated GraphiQL schema; do not promise automatic job creation from this connection alone.
Verify before going live
Run Test connection and one read action against a known permitted record. Then test each intended write in an authorized sandbox. Check the provider’s own record and the Verbatik receipt. Publish the agent after assigning its tools. If a write has an unknown outcome, reconcile it with the vendor before trying again.