Short answer: Drop the "Jobber → Update Jobber Client" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | Required | Jobber client ID (encoded GID). Use List Clients to find it. |
First Name first_name | string | Optional | New first name (leave empty to keep existing) |
Last Name last_name | string | Optional | New last name (leave empty to keep existing) |
Company Name company_name | string | Optional | New company name (leave empty to keep existing) |
{"client_id": "{{trigger.client_id}}","first_name": "{{trigger.first_name}}","last_name": "{{trigger.last_name}}","company_name": "{{trigger.company_name}}"}
{"data": {"clientEdit": {"client": {"id": "Z2lkOi8vSm9iYmVyL0NsaWVudC8x","lastName": "Doe","firstName": "Jane"},"userErrors": []}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.