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 "Create From Template" operation under the "Job" resource 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.
Practical examples include:
- Creating a new service job for a client using a standard job template.
- Automatically generating jobs with preset descriptions and addresses from templates.
- Associating jobs with existing companies or creating new company records on the fly.
Properties
| Name | Meaning |
|---|---|
| Job Template Name or ID | Select a job template by name or UUID from a list loaded dynamically. Alternatively, specify the template ID via expression. |
| Fields | A collection of fields to customize the created job: |
| - job_description | Text description of the job. |
| - job_address | Street address for the job. |
| - company_uuid | UUID of an existing company/client to associate 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 will be 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. The exact structure depends on the API but typically includes job identifiers, status, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ServiceM8 API.
- The node uses the ServiceM8 REST API endpoints to perform operations.
- Network connectivity to the ServiceM8 API endpoint is necessary.
- No additional environment variables are required beyond the API credential.
Troubleshooting
- Missing or invalid job template: If the selected job template does not exist or the ID is incorrect, the API request will fail. Ensure the template exists and the correct identifier is used.
- Conflicting company fields: Providing both
company_uuidandcompany_namesimultaneously will cause the node to ignore the company name field. Use only one to avoid conflicts. - Empty fields: If no fields are provided or all are empty, the job creation may fail or produce incomplete results. Always provide at least the necessary fields.
- API errors: Errors from the ServiceM8 API (e.g., authentication failure, rate limits) will be thrown as node errors. Verify API credentials and usage limits.
- Expression errors: When using expressions to specify template IDs, ensure the expression syntax is correct and resolves to a valid value.