Actions14
- Client Actions
- Email Actions
- Job Actions
- Search Actions
- SMS Actions
Overview
This node integrates with the ServiceM8 platform, allowing users to manage various resources such as clients, jobs, emails, SMS, and searches. Specifically, for the Job resource with the Delete operation, the node deletes a job identified by its UUID from the ServiceM8 system.
Common scenarios where this node is beneficial include automating job lifecycle management, cleaning up obsolete or canceled jobs, and integrating job deletion into broader workflows that maintain data consistency across systems.
For example, after completing a project in an external system, you might use this node to automatically delete the corresponding job in ServiceM8 to keep records tidy.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier (UUID) of the job to be deleted. This string specifies which job will be removed from ServiceM8. |
Output
The node outputs a JSON array containing the response from the ServiceM8 API after attempting to delete the job. Typically, this response confirms the deletion or provides details about the deleted job. The exact structure depends on the API's response but generally includes status information.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ServiceM8 API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses HTTP DELETE requests to the ServiceM8 API endpoint corresponding to the job resource.
Troubleshooting
Common Issues:
- Providing an invalid or empty UUID will cause the deletion to fail.
- Network connectivity problems can prevent the node from reaching the ServiceM8 API.
- Insufficient permissions or expired API tokens may result in authorization errors.
Error Messages:
- "No fields to update were added" — Not applicable for delete but seen in other operations; ensure correct parameters are provided.
- API error responses indicating "Not Found" or "Unauthorized" typically mean the UUID does not exist or credentials are invalid.
Resolution Tips:
- Verify the UUID is correct and corresponds to an existing job.
- Check that the API key or token used has sufficient permissions.
- Ensure network access to the ServiceM8 API endpoints.
- Use the node’s “Continue On Fail” option to handle errors gracefully in workflows.