Actions14
- Client Actions
- Email Actions
- Job Actions
- Search Actions
- SMS Actions
Overview
This node integrates with the ServiceM8 platform, allowing users to perform various operations on different resources such as jobs, clients, emails, SMS, and searches. Specifically, for the Job - Get operation, it retrieves detailed information about a specific job identified by its UUID. This is useful in scenarios where you want to fetch job details for processing, reporting, or further automation within your workflow.
Practical examples include:
- Fetching job details to update a CRM system.
- Retrieving job status before sending notifications.
- Accessing job data to generate invoices or work reports.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier of the job to retrieve. This string value specifies which job's details will be fetched from ServiceM8. |
Output
The node outputs an array of JSON objects representing the job(s) retrieved from ServiceM8. Each object contains all the fields returned by the ServiceM8 API for a job resource, such as job details, status, client info, scheduling, and other metadata.
If multiple jobs are retrieved (in other operations), the output will be an array of such job objects. For the "Get" operation, typically a single job object is returned.
The node does not output binary data.
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 REST API endpoints.
- No additional external dependencies beyond the configured API authentication.
Troubleshooting
Common issues:
- Providing an invalid or empty UUID will result in errors or no data returned.
- Network connectivity problems can cause request failures.
- Insufficient permissions or expired API credentials may lead to authorization errors.
Error messages:
- "No search query was provided." — occurs if a search operation is attempted without specifying a query.
- "No fields to update were added" — relevant for update operations when no update data is provided.
- General HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) indicate credential or resource issues.
Resolutions:
- Ensure the UUID is correctly specified and corresponds to an existing job.
- Verify API credentials and permissions.
- Check network connectivity and API endpoint availability.
- Use the "Continue On Fail" option in the node settings to handle errors gracefully in workflows.