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 clients, jobs, emails, SMS, and searches. Specifically, for the Client - Get operation, it retrieves detailed information about a single client identified by a UUID.
Typical use cases include:
- Fetching client details to enrich workflows with customer data.
- Automating client data retrieval for reporting or CRM synchronization.
- Using client information to trigger further actions in business processes.
For example, you might use this node to get a client's contact details before sending them a personalized email or scheduling a job.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier (UUID) of the client to retrieve. This is a required string input that specifies which client record to fetch from ServiceM8. |
Output
The node outputs an array of JSON objects representing the retrieved client data. Each object contains the full details of the client as returned by the ServiceM8 API, including fields such as name, contact information, address, and any other client-specific metadata.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the client, but this operation focuses on JSON data only.
Dependencies
- Requires an active connection to the ServiceM8 API using an API key credential configured in n8n.
- The node depends on the ServiceM8 REST API endpoints to fetch client data.
- Proper network access and permissions to call the ServiceM8 API are necessary.
Troubleshooting
Common issues:
- Invalid or missing UUID: The node will fail if the UUID parameter is empty or incorrect.
- Authentication errors: If the API key credential is invalid or expired, requests will be rejected.
- Network connectivity problems can cause timeouts or failures when calling the ServiceM8 API.
Error messages:
- "No search query was provided." — Not applicable for this operation but may appear in search operations.
- Errors related to missing fields or invalid parameters usually indicate misconfiguration of input properties.
- API errors from ServiceM8 will be passed through; check the error message for details like "Not Found" if the UUID does not exist.
Resolution tips:
- Verify the UUID value is correct and corresponds to an existing client.
- Ensure the API key credential is valid and has sufficient permissions.
- Check network connectivity and firewall settings.
- Use the "Continue On Fail" option to handle errors gracefully in batch processing.