JActionJobberUpdated September 2026

How do I fetch a Jobber client?

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

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

Get 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
Client ID client_id	string	Required	Jobber client ID

Sample request

{
  "client_id": "{{trigger.client_id}}"
}

Returns

{
  "data": {
    "client": {
      "id": "Z2lkOi8vSm9iYmVyL0NsaWVudC8x",
      "emails": [
        {
          "address": "john@example.com",
          "primary": true
        }
      ],
      "phones": [
        {
          "number": "+15551234567",
          "primary": true
        }
      ],
      "lastName": "Doe",
      "createdAt": "2026-01-15T12:00:00Z",
      "firstName": "John",
      "companyName": null
    }
  }
}

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

Triggered by

Apps that pair well as the trigger for Get 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 Get Jobber Client.

What does the Get Jobber Client action do in Jobber?

Returns a client by ID with contact info, properties, recent jobs. The standard lookup for enrichment workflows.

What inputs does Get Jobber Client require?

Required: Client ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Get Jobber Client support batch operations?

Run Get 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