Service FusionInstall

Summary

Creates a Service Fusion job for the specified customer and returns the API response. You can set scheduling, status, category, source, contacts, assigned techs, priority, payment type, and other job details; custom fields and additional request-body data are optional.

Inputs

• Customer (required) — Customer ID or exact customer name.
• Status Name or ID — Job status; whether it is required depends on company preferences.
• Category Name or ID — Job category.
• Source Name or ID — Lead source.
• Description — Job description.
• Start Date — Job start date; sent as a date.
• Contact First Name — Contact first name. An existing contact with the same first and last name is reused.
• Contact Last Name — Contact last name.
• Assigned Tech Names or IDs — Techs to assign to the job; the node sends their IDs.
• Priority — Low, Normal, or High; leave at the default to omit it.
• Payment Type Name or ID — Payment type; whether it is required depends on company preferences.
• Agent IDs — Comma-separated user IDs to attach as agents.
• Additional Fields — Optional job details, including completion and tech notes, contract, payment terms, duration, end date, follow-up flag, customer note, one job note, phase, PO number, project, promised time window, and service address. Duration is entered in minutes and sent in seconds.
• Custom Fields — Map configured Service Fusion custom fields. The available fields are inferred from recently updated job records; select-field options are entered as free text.
• Custom Fields (JSON) — Custom fields as a name-to-value object or an array of {"name","value"} entries. JSON values override mapped values with the same name and can specify fields not yet present on a record.
• Additional Body (JSON) — Optional JSON object merged into the request body last. Use it for API fields such as products, services, other charges, labor charges, expenses, equipment, or tasks; consult the Service Fusion API for their shapes.

Output shape

A single job record from the Service Fusion API for each input item.

The API response is passed through as the output JSON. If the response is an array, each element becomes a separate output item. With Continue On Fail enabled, failures produce an item containing an error message.

Examples

Example 1: Create a scheduled, high-priority job and assign techs

Supply the required customer, then set the start date, priority, and assigned tech IDs; optionally add status, category, or source.

Example 2: Create a job with line items or custom fields

Map available custom fields or provide them as JSON. Use Additional Body (JSON) for list data such as services, products, or tasks.

Links

• n8n community nodes installation guide