Actions14
- Client Actions
- Email Actions
- Job Actions
- Search Actions
- SMS Actions
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 could 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 against the selected field. |
Filters can be combined with multiple conditions, allowing complex queries to precisely target the desired client subset.
Output
The node outputs an array of JSON objects representing the clients matching the specified filters. Each object corresponds to a single client record as returned by the ServiceM8 API.
The output structure typically includes client details such as:
- Client identifiers
- Contact information
- Status and metadata fields
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ServiceM8 API via an API key credential configured in n8n.
- The node depends on the ServiceM8 REST API endpoints to fetch client data.
- Proper permissions on the API key are necessary to read client information.
Troubleshooting
- No results returned: Ensure that the filter conditions are correctly set and match existing client data. An empty result may indicate no clients meet the criteria.
- Invalid filter field or operator: Use the provided dropdowns to select valid fields and operators. Custom expressions should follow n8n's expression syntax.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Rate limiting or network issues: If requests fail intermittently, check network connectivity and ServiceM8 API rate limits.
Common error messages:
"No search query was provided."— This applies to search operations; ensure required parameters are set."No fields to update were added."— Relevant for update operations; ensure at least one field is specified.