How to get jobber client in Jobber

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.

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

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

More actions