Xubio icon

Xubio

Interactúa con la API de Xubio para operaciones contables con soporte AI

Actions5

Overview

This node integrates with the Xubio API to perform accounting-related operations, specifically focusing on managing clients ("Cliente" resource). The "Obtener" operation allows users to retrieve detailed information about a specific client by their unique ID. This is useful in scenarios where you need to fetch client data for invoicing, reporting, or customer management workflows.

For example, you might use this node to:

  • Retrieve a client's contact and tax information before generating an invoice.
  • Fetch client details to verify account status or update records in another system.
  • Integrate client data retrieval into automated workflows that require up-to-date customer info.

Properties

Name Meaning
ID del Cliente The unique identifier of the client whose information you want to retrieve (required).

Output

The node outputs JSON data representing the client object retrieved from the Xubio API. This typically includes fields such as the client's name, email, phone number, tax identification number (CUIT), and other relevant client details as provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Xubio API.
  • The node depends on the xubioApiRequest helper function to make HTTP requests to the Xubio API endpoints.
  • Proper configuration of the API credentials within n8n is necessary for successful communication.

Troubleshooting

  • Error: "Debe proporcionar un ID de cliente válido"
    This error occurs if the client ID parameter is missing or set to zero. Ensure you provide a valid numeric client ID.

  • Error: "El recurso 'client' no está implementado aún!"
    Indicates an unsupported resource was selected. Confirm that the resource is set to "Cliente" for this operation.

  • Invalid JSON errors in custom configurations (not applicable here but relevant for custom mode)
    If using custom JSON parameters elsewhere, ensure they are well-formed JSON objects.

  • HTTP method or endpoint errors
    For custom operations, invalid HTTP methods or empty endpoints will cause errors. Use one of GET, POST, PUT, DELETE, PATCH and specify a non-empty endpoint.

  • API authentication failures
    Verify that the API key credential is correctly configured and has sufficient permissions.

Links and References

Discussion