Actions5
- Cliente Actions
Overview
This node integrates with the Xubio API to perform operations related to clients ("Cliente"). Specifically, the "Actualizar" (Update) operation allows updating an existing client's information by specifying their unique client ID and the data fields to update.
Typical use cases include:
- Updating customer contact details such as name, email, or phone number.
- Modifying tax identification numbers (CUIT) for clients.
- Keeping client records up-to-date in accounting or CRM workflows.
For example, you might use this node to automatically update a client's email address after receiving new contact info from a form submission or external system.
Properties
| Name | Meaning |
|---|---|
| ID del Cliente | The unique identifier of the client to update. This is required to specify which client to modify. |
| Datos del Cliente | A collection of client data fields to update. Includes: - Nombre: Full name of the client. - Email: Client's email address. - Teléfono: Phone number. - CUIT: Tax identification number. |
Output
The output JSON contains the response from the Xubio API after attempting to update the client. It typically includes the updated client object or confirmation of the update operation.
If an error occurs, the output will contain an error field with the error message.
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 Xubio endpoints.
- No additional external dependencies are needed beyond the configured API authentication.
Troubleshooting
- Missing or invalid client ID: The node throws an error if the client ID is zero or not provided. Ensure you supply a valid numeric client ID.
- Empty update data: If no client data fields are provided to update, the node will throw an error. Provide at least one field to update.
- Invalid JSON in input fields: Although this operation uses structured inputs, if any JSON-based parameters were used (in other operations), invalid JSON would cause errors.
- API errors: Errors returned from the Xubio API (e.g., client not found, permission denied) will be surfaced in the node output. Check the API credentials and client ID validity.
- HTTP method restrictions: The update operation uses HTTP PUT; ensure network connectivity and that the API endpoint is reachable.
Links and References
- Xubio API Documentation (general reference for API endpoints and data formats)
- n8n documentation on creating custom nodes