Actions11
- Job Actions
- Client Actions
- Email Actions
- SMS Actions
Overview
This node integrates with the ServiceM8 platform, allowing users to manage various resources such as Clients, Jobs, Emails, and SMS messages. Specifically, for the Job - Update operation, it updates one or more fields of an existing job identified by its UUID.
Typical use cases include:
- Modifying job details like status, description, or scheduled time after creation.
- Automating updates to jobs based on external triggers or workflows.
- Synchronizing job information from other systems into ServiceM8.
For example, you might update a job’s status to "Completed" once a task is finished or change the assigned staff member dynamically.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier of the job to update. Required to specify which job record to modify. |
| Fields | A collection of fields to update on the job. Each entry includes: |
| - Field Name or ID: Selectable list of job fields available for update (or specify via expression). | |
| - Value: The new value to assign to the selected field. |
The "Fields" property supports multiple entries, allowing batch updates of several fields in one execution.
Output
The node outputs an array of JSON objects representing the updated job records returned from the ServiceM8 API. Each object contains the job's data after the update operation.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ServiceM8 API using an API key credential configured in n8n.
- The node uses HTTP POST requests to the ServiceM8 API endpoints to perform updates.
- Proper permissions on the API key are necessary to modify job records.
Troubleshooting
- No fields to update were added: This error occurs if the "Fields" property is empty or no valid fields are specified. Ensure at least one field with a corresponding value is provided.
- Invalid UUID or job not found: If the UUID does not correspond to an existing job, the API will return an error. Verify the UUID is correct.
- API authentication errors: Check that the API key credential is valid and has sufficient permissions.
- Network or connectivity issues: Ensure the node can reach the ServiceM8 API endpoint without firewall or proxy blocking.
- Expression errors in field names or values: When using expressions, verify their correctness to avoid runtime failures.