JActionJobberUpdated September 2026

How do I add a Jobber client?

Short answer: You can create jobber client in Jobber by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jobber Create Jobber Client action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Jobber Client in Jobber — start free All 7 Jobber actions

Create Jobber Client in Jobber — start free

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.

Triggered by

Apps that pair well as the trigger for Create Jobber Client.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Jobber

2 Google Sheets triggers

HubSpot → Jobber

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Jobber returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Jobber Client support batch operations?

Run Create Jobber Client inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Jobber's rate limits.

More actions