Short answer: You can create jobber client in Jobber by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jobber Create Jobber Client action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
First Name first_name | string | Optional | Client first name |
Last Name last_name | string | Optional | Client last name |
Company Name company_name | string | Optional | Use for commercial clients |
Email email | string | Optional | Primary email address |
Phone phone | string | Optional | Primary phone number |
{"first_name": "John","last_name": "Doe","company_name": "{{trigger.company_name}}","email": "user@example.com","phone": "+15551234567"}
{"data": {"clientCreate": {"client": {"id": "Z2lkOi8vSm9iYmVyL0NsaWVudC8x","lastName": "Doe","firstName": "John","companyName": null},"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.