Actions46
- Attachment Actions
- Attachments in a Transaction Actions
- Beneficiary Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transaction Actions
- Label Actions
- Membership Actions
- Organization Actions
- Request Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
The node integrates with the Qonto API to manage various financial and organizational resources. Specifically, for the Client Invoice resource with the Show Client Invoice operation, it retrieves detailed information about a specific client invoice from the Qonto system.
This node is beneficial in scenarios where you need to automate fetching client invoice details for accounting, reporting, or integration with other business systems. For example, you could use this node to automatically pull invoice data into your CRM or ERP system whenever an invoice is created or updated in Qonto.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Options: "Login and Secret-Key", "OAuth2". |
Note: The provided properties JSON only includes the authentication property. The actual implementation supports many more parameters depending on the resource and operation, but for the Client Invoice - Show Client Invoice operation, the key input would be the identifier of the client invoice to retrieve (not explicitly listed here).
Output
The output is a JSON array containing the response from the Qonto API for the requested client invoice. This typically includes all details of the client invoice such as:
- Invoice number
- Invoice date
- Due date
- Amount
- Currency
- Description
- Status and other metadata
No binary data output is indicated for this operation.
Dependencies
- Requires access to the Qonto API.
- Requires either an API key credential ("Login and Secret-Key") or OAuth2 authentication configured in n8n.
- Uses helper functions (
qontoApiRequestandhandleListing) internally to make HTTP requests to the Qonto API endpoints. - Uses UUID generation for idempotency keys in some operations (not specifically for this one).
Troubleshooting
Common issues:
- Invalid or missing authentication credentials will cause authorization errors.
- Providing an incorrect or non-existent client invoice ID will result in a "not found" error from the API.
- Network connectivity issues can cause request failures.
Error messages:
- Authorization errors: Ensure that the API key or OAuth2 token is valid and has sufficient permissions.
- Not found errors: Verify the client invoice ID parameter is correct.
- Rate limiting or server errors: Retry after some time or check Qonto API status.
Links and References
- Qonto API Documentation — Official API docs for detailed endpoint info.
- n8n Documentation — For general usage of custom nodes and authentication setup.