Jobber

Jobber is a field service management platform for home and commercial service businesses. It handles client management, job scheduling, invoicing, and dispatching. Advanced Form Integration creates clients and jobs in Jobber from your WordPress form submissions using the GraphQL API.

What you’ll need

• An active Jobber account.
• A Jobber Developer App with an OAuth2 Access Token (see below).
• The Advanced Form Integration plugin installed and activated.

Get your Jobber credentials

1. Open the Jobber Developer Center and create (or open) a developer app.
2. Generate an OAuth2 access token for that app.
3. Copy the access token.
4. In WordPress, go to AFI → Settings → Jobber.
5. Click Add Account, paste the access token, and give the account a name.
6. Optional: pin a specific GraphQL version (YYYY-MM-DD) or leave blank to use the bundled default.
7. Click Save.

AFI sends requests to https://api.getjobber.com/api/graphql using Bearer authentication and the X-JOBBER-GRAPHQL-VERSION header.

Create the integration

1. Go to AFI → Add New.
2. Give the integration a name, for example Service request to Jobber.
3. Under Trigger, pick the form plugin and the specific form.
4. Under Action → Platform, select Jobber.
5. In Task, choose Create Client & Job.
6. Pick the saved account in the Jobber Account dropdown.
7. Map your form fields onto the Jobber fields listed below.
8. Optional: open Conditional Logic to limit which submissions are sent.
9. Click Save Integration.

Tasks supported

Create Client & Job

Creates or updates a client and then creates a job linked to that client, using two sequential GraphQL mutations:

1. Client resolution: if an Existing Client ID is mapped, AFI edits that client via clientEdit. Otherwise, if any client fields are mapped, AFI creates a new client via clientCreate and captures the returned client ID.
2. Job creation: creates a job under that client via jobCreate. The Job Title is required; AFI will not send the mutation if it is empty.

Client fields

Job fields

AFI normalizes date/time values to ISO 8601 UTC. If the mapped value is already in ISO format, it passes through unchanged.

Pro features

The Pro integration extends the free version with client and job tags, external IDs, and custom JSON merging for advanced field mapping. Pro uses the same Jobber access token connection.

Tags

Pro adds tag fields for both clients and jobs. Enter tags as comma-separated strings. Trigger tags (e.g. {form_source}) are supported.

External ID

Pro adds a Client externalId field, useful for syncing the Jobber client back to your own system.

Custom JSON merge

Pro provides two raw JSON textareas: one for Client and one for Job payloads. The JSON is deep-merged into the GraphQL mutation input, giving access to fields the basic mapper does not expose (custom fields, line items, job form IDs, schedule attributes, etc.).

Feature comparison

Conditional logic example

Only create Jobber jobs for service requests that include a service address. Add a condition on address_line1 being not empty. General enquiries that do not require a site visit go to an email-only integration.

Troubleshooting

GraphQL errors in the log

AFI parses both top-level errors and per-mutation userErrors from Jobber’s response. The first error message is surfaced in the log entry. Common causes: missing required fields, invalid field names, or an outdated GraphQL API version.

Client created but job not created

The Job Title field is required by Jobber’s API. If it is empty or not mapped, AFI will not send the jobCreate mutation to avoid a guaranteed rejection.

Access token expired

Jobber OAuth2 tokens expire. Regenerate a new token in the Jobber Developer Center and update it in AFI → Settings → Jobber.

Related docs

• Send Contact Form 7 submissions to Jobber
• Send WPForms submissions to Jobber
• Conditional Logic