Create Jobber Client: Jobber action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
First Name first_name	string	Optional	Client first name
Last Name last_name	string	Optional	Client last name
Company Name company_name	string	Optional	Use for commercial clients
Email email	string	Optional	Primary email address
Phone phone	string	Optional	Primary phone number

Sample request

{
  "first_name": "John",
  "last_name": "Doe",
  "company_name": "{{trigger.company_name}}",
  "email": "user@example.com",
  "phone": "+15551234567"
}

Returns

{
  "data": {
    "clientCreate": {
      "client": {
        "id": "Z2lkOi8vSm9iYmVyL0NsaWVudC8x",
        "lastName": "Doe",
        "firstName": "John",
        "companyName": null
      },
      "userErrors": []
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Jobber Client.

What does the Create Jobber Client action do in Jobber?

Creates a new client record. For "lead form submission → push to Jobber" sync workflows in home-service businesses.

What inputs does Create Jobber Client require?

Create Jobber Client has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Jobber returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Jobber Client support batch operations?

Yes. Run Create Jobber Client inside a Loop node to process arrays. Tiny Command handles Jobber's rate limits automatically so you don't have to throttle manually.

More actions