Actions11
- Client Actions
- Job Actions
- Email Actions
- SMS Actions
Overview
This node integrates with the ServiceM8 platform, allowing users to interact with various resources such as Jobs, Clients, Emails, and SMS messages. Specifically, for the Job resource with the Get Many operation, the node retrieves multiple job records from ServiceM8 based on user-defined filters.
Typical use cases include:
- Fetching a list of jobs that meet certain criteria (e.g., jobs created after a specific date or jobs with a particular status).
- Automating workflows that require batch processing or analysis of multiple jobs.
- Integrating job data into other systems or dashboards for reporting purposes.
For example, a user might configure this node to retrieve all jobs where the "status" field equals "completed" to generate a report of finished work.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of filter conditions to narrow down the jobs retrieved. Each filter includes: |
| - Field Name or ID: The job 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, allowing complex queries to fetch exactly the desired subset of jobs.
Output
The node outputs an array of JSON objects representing the jobs retrieved from ServiceM8. Each object corresponds to a single job record with its associated fields as returned by the ServiceM8 API.
If the node is configured to retrieve many jobs, the output will be a concatenated list of all matching job entries.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ServiceM8 API.
- The node depends on the ServiceM8 REST API endpoints to fetch job data.
- No additional external services are required beyond the ServiceM8 API.
- Proper configuration of credentials in n8n is necessary for successful API communication.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using invalid field names or operators in filters may result in errors or empty results.
- Network connectivity issues can prevent the node from reaching the ServiceM8 API.
Error Messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- If no jobs are returned, check that filter values and field names are correct and exist in your ServiceM8 account.
- API rate limits or service outages may cause request failures; retry later or consult ServiceM8 status.