ServiceM8 icon

ServiceM8

ServiceM8 Node
Join our community

Actions11

Overview

This node integrates with the ServiceM8 platform, allowing users to interact with various resources such as Clients, Jobs, Emails, and SMS messages. Specifically, for the Client resource with the Get Many operation, the node fetches multiple client records from ServiceM8 based on user-defined filters.

Typical use cases include:

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

For example, a user might configure this node to get all clients whose status is "active" or whose last update was within the past month.

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 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 single client record with its associated fields as returned by the ServiceM8 API.

If binary data were involved (not applicable here), it would be summarized accordingly, but this operation deals solely with JSON 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 match existing client data. Incorrect field names or values may result in empty responses.

  • Invalid filter field or operator:
    Use the provided dropdown options for fields and operators to avoid invalid queries. Custom expressions should follow n8n's 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 fields to update were added":
    This error does not apply to the Get Many operation but may appear if mistakenly used with update operations without specifying fields.

  • 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