Actions30
- Appointment Actions
- Custom Field Actions
- Customer Actions
- Division Actions
- Proposal Actions
- Job Actions
- Note Actions
- Referral Actions
- Task Actions
- Trade Actions
- User Actions
- Workflow Actions
Job → Create
AI-generatedSummary
Create a Leap job for a customer, optionally assigning trades, a division, representatives, a workflow stage, job-site details, and custom fields. The node posts the job to Leap and, if a stage is specified and the created record has an ID, makes a separate request to set that stage.
Inputs
- Customer ID (required) — Leap customer ID to associate with the job.
- Name (required) — Job name or title.
- Description — Job description or notes.
- Trade Names or IDs — Trades for the job; select multiple names or provide IDs.
- Division Name or ID — Division for the job; select a division or provide its ID.
- Rep Names or IDs — Sales representatives assigned to the job; select multiple or provide IDs.
- Stage Name or ID — Workflow stage to set after job creation. Applied in a separate request.
- Address, City, Country Name or ID, State Name or ID, ZIP / Postal Code — Optional job-site address details. The state list depends on the country and defaults to United States when no country is selected.
- Additional Fields — Optional address line 2, alternate ID, appointment and call requirements, completion and contract signed dates, duration, estimators, insurance flag, lead number, same-as-customer-address flag, and subcontractors.
- Custom Fields — Map job custom fields loaded from the Leap account. Setting custom fields replaces the job's existing custom field values. User fields accept comma-separated user IDs; dropdown mapping supports top-level options.
Output shape
A single job record per input item.
Returns the API's data field when present, otherwise the full response. When a stage is set and the created record has an ID, the returned record also gets stage_id. If continue-on-fail is enabled, a failed item returns an error object.