Actions65
- Calendar Actions
- Company Settings Actions
- Contact Actions
- Estimate Actions
- Job Actions
- Create
- Get
- Get Many
- Search
- Get Contacts
- Get Milestone History
- Get History
- Get Initial Appointment
- Get Payments
- Get Financials
- Set Sales Owner
- Set Company Representative
- Set Initial Appointment
- Get Custom Fields
- Set Custom Fields
- Update Priority
- Update Address
- Update Category
- Update Lead Source
- Update Work Type
- Update Trade Types
- Update Insurance
- Update Adjuster
- Lead Actions
- Supplement Actions
- User Actions
- Webhook Actions
Job → Create
AI-generatedSummary
Create an AccuLynx job for the required contact, with optional trade types, lead source, category, work type, priority, notes, project address, company representative, and custom fields. Lookup fields accept dropdown selections or supported names/IDs; representative assignment and custom fields are applied in follow-up API calls after creation.
Inputs
- Contact ID (required) — AccuLynx ID of the contact the job is for.
- Trade Types — One or more trade type selections, IDs, names, or comma-separated names.
- Lead Source — Lead source selection, ID, or name; nested sources can be resolved by name.
- Job Category — Job category selection, ID, or name.
- Work Type — Work type selection, ID, or name.
- Company Representative — Optional user selection, UUID, email, or full name. If set, the node assigns the representative after job creation.
- Priority — Normal, High, or Urgent; may be left unset.
- Notes — Free-text notes, up to 1,000 characters per the UI description.
- Project Address — Optional street lines, city, state, ZIP code, and country for the job location.
- Custom Fields — Optional custom field values set in a follow-up request after job creation.
- Additional Fields (Legacy) — Compatibility inputs for older workflows. Top-level values take precedence; this collection is superseded for new workflows.
Output shape
A single job response object, returned as an n8n item.
The job is created first. If a company representative or custom field values are supplied, the node makes additional API calls to apply them. A representative assignment failure is attached to the job response rather than discarding the created job.