Short answer: Drop the "Jobber → Create Jobber Job" 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 | ID of the client this job belongs to |
Job Title title | string | Required | Short description shown on the job card |
Job Description description | string | Optional | Long-form details about the work |
Start Date start_date | string | Optional | Scheduled start date (YYYY-MM-DD) |
End Date end_date | string | Optional | Scheduled end date (YYYY-MM-DD) |
{"client_id": "{{trigger.client_id}}","title": "{{trigger.title}}","description": "{{trigger.description}}","start_date": "2026-04-15","end_date": "2026-04-16"}
{"data": {"jobCreate": {"job": {"id": "Z2lkOi8vSm9iYmVyL0pvYi8x","title": "Lawn mowing","endDate": "2026-04-15","jobNumber": "JOB-101","startDate": "2026-04-15"},"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.