ServiceM8 icon

ServiceM8

ServiceM8 Node
Join our community

Actions14

Overview

This node integrates with the ServiceM8 platform to perform various operations on different resources. Specifically, for the Search resource and the Search operation, it allows users to perform object-specific searches within ServiceM8 data. This is useful when you want to query and retrieve records such as jobs, companies, assets, or other object types based on a search string.

Typical use cases include:

  • Searching for jobs matching a keyword or phrase.
  • Finding companies or assets by name or other attributes.
  • Limiting the number of results returned to optimize workflow performance.

For example, you might use this node to find all jobs related to "plumbing" and then process those jobs further in your automation.

Properties

Name Meaning
Fields A collection of search options:
- Search Query (q) The text string to search for within the selected object type.
- Object Type (objectType) The category of objects to search. Options include: Asset, Attachment, Company, Form Response, Job, Knowledge Article, Material, Material Bundle. Default is "Job".
- Limit Maximum number of search results to return. Must be at least 1. Default is 50.

Output

The node outputs an array of JSON objects representing the search results returned from the ServiceM8 API. Each item corresponds to one matched record of the specified object type.

  • The json output field contains the raw data of each found object.
  • No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the ServiceM8 API using an API key credential configured in n8n.
  • The node uses HTTP requests to the ServiceM8 endpoints to perform searches.
  • No additional external dependencies are required beyond the API access.

Troubleshooting

  • No search query was provided error: If the "Search Query" (q) field is empty, the node will throw an error indicating that no search query was provided. Ensure you specify a non-empty search string.
  • API authentication errors: If the API key credential is missing or invalid, the node will fail to connect. Verify your API credentials in n8n settings.
  • Empty results: If no matches are found, the output will be an empty array. Try broadening your search query or checking the object type.
  • Limit value issues: Setting the limit below 1 may cause errors. Use a positive integer for the limit.

Links and References

Discussion