JActionJobberUpdated September 2026

How do I list Jobber clients?

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

List Jobber Clients in Jobber — start free All 7 Jobber actions

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

Triggered by

Apps that pair well as the trigger for List Jobber Clients.

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

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