ServiceM8 icon

ServiceM8

ServiceM8 Node
Join our community

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 - Get operation, it retrieves detailed information about a single job identified by its UUID. This is useful in scenarios where you need to fetch up-to-date job details from ServiceM8 for further processing, reporting, or automation workflows.

Practical examples:

  • Automatically retrieving job details when a new job is created in ServiceM8 to update an external CRM.
  • Fetching job status and information to trigger notifications or follow-up actions.
  • Integrating job data into custom dashboards or analytics tools.

Properties

Name Meaning
UUID The unique identifier (UUID) of the job to retrieve. This string property specifies which job's details will be fetched from ServiceM8.

Output

The node outputs an array of JSON objects representing the retrieved job(s). For the "Get" operation on a Job resource, the output JSON contains the full details of the specified job as returned by the ServiceM8 API. This typically includes fields such as job ID, client info, status, scheduled times, notes, and other job-specific metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the ServiceM8 API.
  • The node makes HTTP requests to the ServiceM8 REST API endpoints.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Providing an invalid or empty UUID will result in failure to retrieve the job.
    • Network connectivity problems or incorrect API credentials can cause authentication errors.
    • If the job UUID does not exist, the API may return an error or empty response.

  • Error messages and resolutions:

    • "No fields to update were added" — Not applicable for "Get" but appears for update operations if no update fields are provided.
    • API errors related to authorization usually indicate misconfigured or expired API keys; verify and update credentials.
    • If the node throws an error about missing parameters, ensure the UUID field is correctly set and not left blank.

Links and References

Discussion