Actions5
- Cliente Actions
Overview
This node integrates with the Xubio API to perform various operations related to clients ("Cliente" resource). Specifically, the "Obtener Varios" (Get All) operation allows users to retrieve multiple client records from Xubio with optional filtering. This is useful for workflows that need to fetch lists of clients based on criteria such as active status, client status, or name matching.
Practical examples include:
- Fetching all active clients to send a marketing email campaign.
- Retrieving clients filtered by name or status for reporting or synchronization with other systems.
- Automating data extraction for accounting or CRM purposes.
Properties
| Name | Meaning |
|---|---|
| Filtros | Collection of filters to narrow down the clients returned. Options: |
| - Activo: Filter by active status; values: "Activo" (1), "Inactivo" (0) | |
| - Es Cliente: Filter by client status; values: "Sí" (1), "No" (0) | |
| - Nombre: Filter by client name (string) |
These filters are optional and allow precise control over which clients are retrieved.
Output
The output is a JSON array where each item represents a client object returned by the Xubio API. Each client object contains fields as provided by the API, typically including identifiers, names, statuses, and other client-related data.
The node does not explicitly handle binary data for 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 external dependencies beyond the configured API credentials and network access to Xubio.
Troubleshooting
- Invalid or missing client ID: For operations requiring a client ID (not applicable to "Obtener Varios"), errors will be thrown if the ID is zero or invalid.
- Invalid JSON in filters: If filter parameters are malformed JSON, the node will throw an error indicating invalid JSON format.
- Empty endpoint or unsupported HTTP method: In custom mode, if the endpoint is empty or the HTTP method is invalid, the node will raise an error.
- API request failures: Network issues or authentication problems may cause request failures; ensure the API key is valid and network connectivity is stable.
- No clients returned: If filters are too restrictive, the result may be an empty array.
To resolve these issues:
- Verify input parameters and JSON formatting.
- Confirm API credentials are correctly set up.
- Adjust filters to broaden the search if no results are returned.
Links and References
- Xubio API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes