Actions5
- Cliente Actions
Overview
This node integrates with the Xubio API to perform accounting-related operations, specifically managing clients ("Cliente" resource). The "Eliminar" (delete) operation allows users to delete a client by specifying its unique ID. This is useful in scenarios where you need to remove outdated or incorrect client records from your accounting system.
Practical example:
- Automatically deleting a client record when it is no longer active or relevant, triggered by an external event or workflow.
Properties
| Name | Meaning |
|---|---|
| ID del Cliente | The unique identifier of the client to be deleted. Must be a valid number greater than 0. |
Output
The output JSON contains the response from the Xubio API after attempting to delete the specified client. Typically, this will include confirmation of deletion or error details if the operation failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Xubio API.
- The node uses internal helper functions to make HTTP requests to the Xubio endpoints.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Error: "Debe proporcionar un ID de cliente válido para eliminar"
This error occurs if the client ID is missing or zero. Ensure you provide a valid numeric client ID.Invalid JSON errors (not directly related to delete but possible in other operations):
If using custom JSON parameters elsewhere, ensure they are well-formed JSON objects.HTTP method errors:
The node validates HTTP methods; if an invalid method is configured in custom mode, it will throw an error.API errors:
If the API returns an error (e.g., client not found), the node will propagate that message. Verify the client ID exists and the API credentials have sufficient permissions.
Links and References
- Xubio API Documentation (general reference for endpoints and usage)
- n8n documentation on creating custom nodes