ServiceM8 icon

ServiceM8

ServiceM8 Node

Actions14

Overview

This node integrates with the ServiceM8 platform, specifically focusing on managing "Job" resources. The "Get Many" operation retrieves multiple job records from ServiceM8 based on user-defined filters. This is useful for scenarios where you need to fetch a list of jobs matching certain criteria, such as jobs created after a specific date, jobs assigned to a particular staff member, or jobs with a certain status.

Practical examples include:

  • Fetching all open jobs scheduled for the current week.
  • Retrieving jobs filtered by client or location.
  • Extracting jobs that have a specific custom field value for reporting or automation purposes.

Properties

Name Meaning
Filters A collection of filter conditions to narrow down the jobs retrieved. Each filter includes:
- Field Name or ID: Select a job field to filter by (loaded dynamically).
- Operator: Choose how to compare the field value (Equal To, Not Equal, Greater Than, Less Than).
- Value: The value to compare against the selected field.

Output

The output is an array of JSON objects representing the jobs retrieved from ServiceM8. Each object corresponds to a single job and contains its properties as returned by the ServiceM8 API.

  • The json output field holds the job data.
  • There is no binary data output in this operation.

Dependencies

  • Requires an API key credential for authenticating with the ServiceM8 API.
  • The node uses the ServiceM8 REST API endpoints to fetch job data.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • No jobs returned: Ensure that the filter criteria are correct and match existing jobs in your ServiceM8 account.
  • Invalid filter field or operator: Use the dynamic dropdowns to select valid fields and operators; avoid manually entering unsupported values.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Rate limits or API errors: If the API returns errors due to rate limiting or server issues, consider adding retry logic or checking ServiceM8 service status.
  • Empty filter collection: If no filters are set, the node may return all jobs, which could be large; use filters to limit results.

Links and References

Discussion