How to list jobber jobs in Jobber

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	Optional	Filter to jobs for a specific client
Limit limit	number	Optional	Max jobs to return

Sample request

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

Returns

{
  "data": {
    "jobs": {
      "nodes": [
        {
          "id": "Z2lkOi8vSm9iYmVyL0pvYi8x",
          "title": "Lawn mowing",
          "endDate": "2026-04-15",
          "jobNumber": "JOB-101",
          "jobStatus": "scheduled",
          "startDate": "2026-04-15"
        }
      ]
    }
  }
}

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

FAQ

Questions about List Jobber Jobs.

What does the List Jobber Jobs action do in Jobber?

Paginated jobs with filters by status, date, client. For "this week's scheduled jobs" capacity-planning workflows.

What inputs does List Jobber Jobs require?

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

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

More actions