VendusInstall

Overview

This node integrates with the Vendus API, a platform for invoicing and business management. Specifically, the "Get Client Resume" operation under the "Client" resource retrieves detailed summary information about a specific client identified by their name or ID. This can be useful in scenarios where you want to fetch a client's financial overview, transaction history, or other aggregated data to display in dashboards, generate reports, or trigger further automation workflows based on client status.

For example, a user might use this node to:

• Automatically retrieve a client's outstanding balance and recent invoices before creating a new order.
• Fetch client resume details to update CRM records or send personalized communications.
• Monitor client activity and payment status as part of an automated credit control process.

Properties

Output

The node outputs JSON data representing the client's resume information as returned by the Vendus API. This typically includes aggregated client data such as balances, transaction summaries, and other relevant client metrics. The exact structure depends on the Vendus API response for the client resume endpoint.

No binary data output is produced by this operation.

Example output JSON (simplified):

{
  "id": "123",
  "name": "Client Name",
  "balance": 1500.00,
  "invoices": [...],
  "payments": [...],
  ...
}

Dependencies

• Requires an API key credential configured in n8n to authenticate requests against the Vendus API.
• The node uses the base URL provided in the credentials to construct API requests.
• Optional debug logging requires no additional dependencies but helps trace request/response details.

Troubleshooting

• Missing or invalid Client ID: If the client identifier is not provided or incorrect, the node will throw an error indicating the parameter is required or that the client was not found.
• API authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
• Network or API errors: Enabling debug logging can help identify issues such as incorrect URLs, HTTP method mismatches, or unexpected API responses.
• No routing configuration found: This internal error indicates a misconfiguration in the node parameters; verify that the Resource is set to "Client" and Operation to "Get Client Resume".

Links and References

• Vendus API Documentation (as referenced in the node description)
• n8n Expressions Documentation – for using expressions in input fields