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 - Delete operation, it enables deleting a job identified by its UUID from the ServiceM8 system.
Common scenarios include:
- Automating cleanup of completed or canceled jobs.
- Integrating job deletion into workflows that manage job lifecycle.
- Removing test or duplicate jobs programmatically.
Example: Automatically delete a job after its completion confirmation in another system.
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 output is a JSON array containing the response from the ServiceM8 API after the delete request. Typically, this will confirm the deletion or provide 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 using an API key credential configured in n8n.
- The node uses HTTP requests to the ServiceM8 REST API endpoints.
- Proper permissions on the API key are necessary to perform delete operations on jobs.
Troubleshooting
Common issues:
- Providing an invalid or empty UUID will cause the API call to fail.
- Insufficient permissions on the API key may result in authorization errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- "No fields to update were added" — Not applicable for delete but seen in update operations; ensure correct parameters.
- API error responses typically include HTTP status codes and messages indicating the problem (e.g., 404 if job not found).
Resolution tips:
- Verify the UUID is correct and corresponds to an existing job.
- Check API credentials and their permissions.
- Ensure network access to the ServiceM8 API endpoint.
- Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.