Actions45
- Attachment Actions
- Beneficiary Actions
- Business Account Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transfer Actions
- Label Actions
- Membership Actions
- Organization Actions
- Quote Actions
- Request Actions
- SEPA Transfer Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
The node integrates with the Qonto API to perform operations on various financial resources. Specifically, for the Client Invoice resource with the Get One operation, it retrieves a single client invoice by its unique ID. This is useful in scenarios where you need to fetch detailed information about a specific invoice, such as verifying payment status, reviewing invoice details, or integrating invoice data into other workflows.
Practical examples include:
- Automatically fetching an invoice's details after receiving a payment notification.
- Integrating invoice data into accounting or CRM systems.
- Validating invoice information before processing refunds or credits.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Available option: "API Key" |
| ID | The unique identifier of the client invoice to retrieve. Must be provided as a string. |
Output
The node outputs JSON data representing the retrieved client invoice. The structure typically includes all relevant invoice fields as returned by the Qonto API, such as invoice number, date, amount, status, client details, and line items.
If the node encounters an error (e.g., invalid ID or authentication failure), the output JSON will contain an error field with the error message.
No binary data output is indicated for this operation.
Dependencies
- Requires access to the Qonto API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for API requests depends on the environment (sandbox or production) set in credentials.
- Network connectivity to Qonto endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing invoice ID: The node will throw an error if the ID parameter is empty or incorrect.
- Authentication failures: Ensure the API key is valid and has sufficient permissions.
- Network timeouts or connectivity problems may cause request failures.
Error messages:
"Unknown resource: clientInvoice": Indicates a misconfiguration or typo in the resource name.- Errors returned from the Qonto API (e.g., "Invoice not found") will appear in the output JSON under the
errorfield if "Continue On Fail" is enabled.
Resolutions:
- Double-check the invoice ID value.
- Verify API key validity and permissions.
- Confirm network access to Qonto API endpoints.
- Enable "Continue On Fail" to handle errors gracefully within workflows.
Links and References
- Qonto API Documentation
- n8n documentation on creating custom nodes