Actions14
- Client Actions
- Email Actions
- Job Actions
- Search Actions
- SMS Actions
Overview
This node integrates with the ServiceM8 platform to manage jobs and related entities. Specifically, the Job - Create From Template operation allows users to create a new job based on an existing job template. This is useful for automating job creation when you have predefined templates that standardize job details, saving time and ensuring consistency.
Typical use cases include:
- Automatically creating service jobs from templates when a new client request arrives.
- Generating repeatable job entries with preset descriptions, addresses, and company information.
- Streamlining workflows by programmatically instantiating jobs without manual data entry.
For example, a field service company could use this node to create a new job for a routine maintenance task using a saved template, filling in specific client or location details dynamically.
Properties
| Name | Meaning |
|---|---|
| Job Template Name or ID | Select a job template from a list or specify its ID via expression. The template defines the base job structure. |
| Fields | A collection of fields to customize the created job: |
| - job_description | Text description of the job. |
| - job_address | Street address where the job will take place. |
| - company_uuid | UUID of the company/client associated with the job. Cannot be used together with Company Name. |
| - company_name | Name of the company/client. If it exists, it will be used; otherwise, a new company is created. Cannot be used together with Company UUID. |
Output
The node outputs an array of JSON objects representing the created job(s). Each object contains the response data returned by the ServiceM8 API after creating the job from the specified template. This typically includes job identifiers, status, timestamps, and any other metadata provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ServiceM8 API with valid API authentication credentials configured in n8n.
- The node uses the ServiceM8 REST API endpoints to fetch job templates and create jobs.
- The "Job Template Name or ID" property relies on dynamic loading of available job templates from the ServiceM8 account.
Troubleshooting
- Missing or invalid job template: If the specified job template does not exist or the ID is incorrect, the API call will fail. Ensure the template is available in your ServiceM8 account and the correct identifier is used.
- Conflicting company fields: Providing both
company_uuidandcompany_namesimultaneously will cause the node to remove the company name before sending the request. To avoid confusion, provide only one of these fields. - Empty fields: If required fields are missing or empty, the API may reject the request. Make sure to fill in necessary job details such as description or address if applicable.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or rate limiting issues: ServiceM8 API limits or network problems can cause failures. Check connectivity and API usage quotas.
Error messages thrown by the node generally reflect the underlying API response and include HTTP error codes and descriptive messages. Review these messages to identify the root cause.