JActionJobberUpdated September 2026

How do I update a Jobber job?

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

Update Jobber Job in Jobber — start free All 7 Jobber actions

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

Triggered by

Apps that pair well as the trigger for Update Jobber Job.

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

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