Actions11
- Client Actions
- Job Actions
- Email 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, and SMS messages. Specifically, for the Client - Get operation, it retrieves detailed information about a single client identified by a UUID.
Common scenarios where this node is beneficial include:
- Fetching client details to use in workflows that require client-specific data.
- Automating client data retrieval for reporting or synchronization with other systems.
- Triggering subsequent actions based on client information fetched from ServiceM8.
For example, you might use this node to get a client's contact details before sending them a personalized email or SMS, or to update your CRM system with the latest client information.
Properties
| Name | Meaning |
|---|---|
| UUID | The unique identifier (UUID) of the client to retrieve. This string value 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 attributes available via the API.
If the node supports binary data output (not indicated for this operation), it would typically represent attachments or media related to the client, but for the "Get Client" operation, only JSON data is returned.
Dependencies
- Requires an API key credential for authenticating with the ServiceM8 API.
- The node makes HTTP requests to the ServiceM8 REST API endpoints.
- Proper configuration of the API credentials within n8n is necessary for successful execution.
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 incorrect API credentials will lead to authentication errors.
Error messages:
- "No fields to update were added" — Not applicable for the Get operation but indicates missing required input when updating.
- API errors returned from ServiceM8 will be surfaced; ensure the UUID exists and the API key has access rights.
Resolution tips:
- Verify the UUID is correct and corresponds to an existing client.
- Check that the API key credential is valid and has appropriate permissions.
- Enable "Continue On Fail" if you want the workflow to proceed despite individual item errors.