ServiceM8 icon

ServiceM8

ServiceM8 Node

Actions11

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 - Delete operation, it enables deleting a job from the ServiceM8 system by specifying its unique identifier (UUID). This is useful in scenarios where jobs are no longer needed or were created in error and must be removed to keep the system clean and up-to-date.

Practical examples include:

  • Automatically removing canceled jobs from ServiceM8.
  • Cleaning up test or temporary jobs after processing.
  • Integrating with other workflows that require job deletion based on certain conditions.

Properties

Name Meaning
UUID The unique identifier of the job to delete. This string value specifies which job will be removed from the ServiceM8 system.

Output

The node outputs a JSON array containing the response from the ServiceM8 API after attempting to delete the specified job(s). The structure typically reflects the API's confirmation of deletion or any relevant metadata returned by the DELETE request.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the ServiceM8 API.
  • Needs an API authentication token credential configured in n8n 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 API to reject the deletion request.
    • Network connectivity problems can prevent successful communication with the ServiceM8 API.
    • Insufficient permissions or expired API credentials may result in authorization errors.

  • Error messages and resolutions:

    • "No fields to update were added" — Not applicable for delete but seen in update operations; ensure required parameters are provided.
    • API errors related to "Not Found" usually indicate the UUID does not correspond to any existing job.
    • Authorization errors suggest checking and refreshing the API key credential.
    • If the node fails and continueOnFail is disabled, the workflow stops; enabling it allows processing subsequent items despite failures.

Links and References

Discussion