Create job
Identifier and availability
- Type:
action - Stable identifier:
service_job:create - Status: Selectable — available in the new-node selector and importable.
Purpose
Creates a visit and stores it in automation context.
Prerequisites and context
Required configuration: settings. Review the available context below before using variables.
Parameters
| JSON path | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
settings |
object | Yes | — | — | Node-specific settings. Unknown keys are rejected. |
settings.contact_id |
runtime_id_template | No | — | — | Use exactly {{contact.id}} or a full {{webhook.path}} variable. Omit to use the current contact. Literal database IDs are rejected. |
settings.scheduled_date |
datetime | No | — | — | Parseable scheduled date/date-time, documented date token, or full {{webhook.path}} variable. |
settings.start_time |
datetime | No | — | — | Parseable visit start date-time, documented date token, or full {{webhook.path}} variable. |
settings.end_time |
datetime | No | — | — | Parseable visit end date-time after start_time, documented date token, or full {{webhook.path}} variable. |
settings.technician |
semantic_or_template | No | — | — | User name, email, or variable placeholder. Literal database IDs are rejected. |
settings.status |
string | No | — | — | Status |
settings.paid_status |
string | No | — | — | Paid status |
settings.notes |
string | No | — | — | Notes |
Unknown parameter and settings keys are rejected. Resource references use names, emails, document keys, or endpoints rather than database IDs.
Inputs and available variables
This node declares no additional variable groups. The always-available date group and context inherited from its path still apply.
Templated strings use double braces, for example {{contact.first_name}}. Availability in the editor does not create runtime context; the trigger and preceding branch still need to provide it.
Connections and branches
This is a sequential action with no branch ports. A root placement uses from set to null and branch set to actions; a branch placement uses the branching action key and branch token. Use a 1-based order within that path.
Connection fragment:
{
"from": null,
"to": "action_service_job_create",
"branch": "actions",
"order": 1
}
Valid JSON node example
{
"key": "action_service_job_create",
"type": "action",
"name": "service_job:create",
"display_name": null,
"parameters": {
"settings": {
"contact_id": "{{contact.id}}",
"scheduled_date": "2026-09-03",
"start_time": "2026-09-03T09:00",
"end_time": "2026-09-03T10:00",
"technician": "alex@example.com",
"status": "Scheduled",
"paid_status": "unpaid",
"notes": "Created by Automation."
}
}
}
Validation and runtime caveats
Date/time settings must parse after variable replacement. When both are supplied, end_time must be later than start_time; scheduling and technician mutations are transactional.
See the Automation JSON import format for the envelope, dependency resolution, graph rules, complete examples, and AI author checklist.