Actions14
Overview
This node integrates with the "Gestor Clientes Max" API to manage clients, appointments, and financial accounts. Specifically for the Cliente (Client) Delete operation, it allows users to delete a client by their unique ID. This is useful in scenarios where you need to remove outdated or incorrect client records from your system.
Practical examples include:
- Automatically deleting client records when they unsubscribe or request data removal.
- Cleaning up test or duplicate client entries in bulk workflows.
- Integrating with other systems to synchronize client deletions.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique numeric identifier of the client to be deleted. |
Output
The output JSON contains the response from the API after attempting to delete the client. Typically, this will be an object indicating success or failure of the deletion operation. The exact structure depends on the API but usually includes status information or confirmation messages.
No binary data output is produced by this operation.
Example output JSON might look like:
{
"success": true,
"message": "Client deleted successfully"
}
or, in case of failure:
{
"error": "Client not found"
}
Dependencies
- Requires an API key credential for authenticating with the Gestor Clientes Max API.
- The node expects the API base URL and API key to be configured in the credentials.
- Network access to the Gestor Clientes Max API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Client ID: The node requires a valid numeric client ID; ensure this is provided.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network connectivity problems: Ensure the n8n instance can reach the API endpoint.
Common error messages:
"Unknown operation: client.delete": Indicates a misconfiguration in the operation name; verify the selected operation.- HTTP 404 or "Client not found": The specified client ID does not exist; confirm the client ID is correct.
- HTTP 401 Unauthorized: API key is invalid or expired; update the credential.
To resolve errors, check input parameters, credentials, and network connectivity.
Links and References
- Gestor Clientes Max API Documentation (replace with actual link if available)
- n8n documentation on Creating Custom Nodes