ServiceM8 icon

ServiceM8

ServiceM8 Node

Actions14

Overview

This node integrates with the ServiceM8 platform, primarily to manage various resources such as clients, jobs, emails, SMS, and searches. Specifically, for the Client resource with the Get Many operation, it retrieves multiple client records from ServiceM8 based on user-defined filters.

Typical use cases include:

  • Fetching a list of clients that meet certain criteria (e.g., clients created after a specific date or clients in a particular location).
  • Automating workflows that require bulk processing or analysis of client data.
  • Synchronizing client data between ServiceM8 and other systems.

For example, you might use this node to get all clients whose status is "active" or whose last update was within the past month, then pass that data downstream for reporting or notification purposes.

Properties

Name Meaning
Filters A collection of filter conditions to narrow down the clients retrieved. Each filter includes:
- Field Name or ID: The client field to filter by (selectable from available fields).
- Operator: The comparison operator to apply (Equal To, Not Equal, Greater Than, Less Than).
- Value: The value to compare the field against.

Filters can be combined with multiple conditions to refine the query.

Output

The node outputs an array of JSON objects representing the clients retrieved from ServiceM8. Each object corresponds to a client record with its associated fields as returned by the ServiceM8 API.

If no clients match the filters, the output will be an empty array.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the ServiceM8 API.
  • The node uses the ServiceM8 REST API endpoints to fetch data.
  • No additional external dependencies are required beyond the configured API credentials.

Troubleshooting

  • No results returned:
    Ensure that the filter conditions are correctly specified and that matching clients exist in ServiceM8. Check for typos or incorrect field names.

  • Invalid filter field or operator:
    Use the provided dropdown options for fields and operators to avoid invalid inputs. Custom expressions are supported but must follow n8n expression syntax.

  • API authentication errors:
    Verify that the API key credential is valid and has sufficient permissions to access client data.

  • NodeOperationError with message "No search query was provided."
    This error is not relevant for the Get Many operation but may appear if using search operations without specifying a query.

  • Continue On Fail behavior:
    If enabled, the node will continue processing subsequent items even if one fails, returning error details alongside successful results.

Links and References

Discussion