Update Jobber Job: 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
Job ID job_id	string	Required	Jobber job ID
Job Title title	string	Optional	Leave empty to keep existing title
Job Description description	string	Optional	Leave empty to keep existing description

Sample request

{
  "job_id": "{{trigger.job_id}}",
  "title": "{{trigger.title}}",
  "description": "{{trigger.description}}"
}

Returns

{
  "data": {
    "jobEdit": {
      "job": {
        "id": "Z2lkOi8vSm9iYmVyL0pvYi8x",
        "title": "Lawn mowing — updated",
        "jobNumber": "JOB-101"
      },
      "userErrors": []
    }
  }
}

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

FAQ

Questions about Update Jobber Job.

What does the Update Jobber Job action do in Jobber?

Updates job fields — status, notes, assignment. For cascading workflow patterns or for syncing external-system state back to Jobber.

What inputs does Update Jobber Job require?

Required: Job 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 Update Jobber Job support batch operations?

Yes. Run Update Jobber Job 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