List Jobber Clients: 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
Search search	string	Optional	Match against client name or company
Limit limit	number	Optional	Max clients to return

Sample request

{
  "search": "{{trigger.search}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "data": {
    "clients": {
      "nodes": [
        {
          "id": "Z2lkOi8vSm9iYmVyL0NsaWVudC8x",
          "emails": [
            {
              "address": "john@example.com",
              "primary": true
            }
          ],
          "lastName": "Doe",
          "firstName": "John",
          "companyName": null
        }
      ]
    }
  }
}

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

FAQ

Questions about List Jobber Clients.

What does the List Jobber Clients action do in Jobber?

Paginated clients with filters. For sync workflows that mirror Jobber clients to other systems.

What inputs does List Jobber Clients require?

List Jobber Clients 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 List Jobber Clients support batch operations?

Yes. Run List Jobber Clients 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