Actions14
- Client Actions
- Email Actions
- Job Actions
- Search Actions
- SMS Actions
Job → Get Many
AI-generatedOverview
This node integrates with the ServiceM8 platform, focusing on managing "Job" resources. Specifically, the "Get Many" operation retrieves multiple job records from ServiceM8 based on user-defined filters. This is useful for scenarios where you need to fetch a list of jobs matching certain criteria, such as jobs created after a specific date, jobs assigned to a particular employee, or jobs with a certain status.
Practical examples include:
- Fetching all open jobs for a given client.
- Retrieving jobs scheduled within a date range.
- Extracting jobs filtered by custom fields for reporting or automation workflows.
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 job fields). | |
| - Operator: The comparison operator to apply. Options are Equal To, Not Equal, Greater Than, and Less Than. | |
| - Value: The value to compare the field against. |
Filters can be combined with multiple conditions to refine the query.
Output
The output is an array of JSON objects, each representing a job record retrieved from ServiceM8. Each object contains the job's data fields as returned by the ServiceM8 API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ServiceM8 API.
- The node uses the ServiceM8 REST API endpoints to fetch job data.
- No additional environment variables are required beyond the API authentication setup in n8n.
Troubleshooting
- No results returned: Ensure that the filter conditions are correctly specified and match existing job data. Incorrect field names or values may result in empty responses.
- Invalid filter field: If a filter field does not exist or is misspelled, the API may return an error or no data. Use the provided options list to select valid fields.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Rate limiting or network issues: Temporary failures may occur due to API rate limits or connectivity problems. Retry or check network settings if errors persist.
- Error message "No search query was provided": This applies to search operations, not "Get Many". For "Get Many", ensure filters are properly set.
Links and References
- ServiceM8 API Documentation
- n8n Expressions Documentation (for using expressions in filter values)