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
This node integrates with the Qonto API to create a client invoice within a specified organization. It is useful for automating invoicing workflows, such as generating invoices for clients directly from your business systems or CRM platforms. For example, after closing a sale, you can automatically create and send an invoice to the client without manual entry.
The "Create a Client Invoice" operation requires details like invoice number, dates, amount, currency, and optional description, then sends this data to Qonto to generate the invoice record.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API: either "Login and Secret-Key" or "OAuth2". |
| Organization ID | The unique identifier of the organization where the client invoice will be created. |
| Client Invoice | A collection of details about the invoice to create, including: |
| - Invoice Number | Unique number identifying the client invoice. |
| - Invoice Date | Date when the invoice is issued. |
| - Due Date | Payment due date for the invoice. |
| - Amount | Monetary amount of the invoice. |
| - Currency | Currency code (e.g., EUR) for the invoice amount. |
| - Description | Optional text describing the invoice or additional details. |
Output
The node outputs JSON data representing the response from the Qonto API after creating the client invoice. This typically includes the newly created invoice's details such as its ID, status, and all submitted fields.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Qonto API.
- Requires valid authentication credentials configured in n8n, either via an API key credential or OAuth2 token.
- The node uses UUID generation internally to handle idempotency keys for safe API requests.
Troubleshooting
- Missing or invalid Organization ID: Ensure the organization ID is correct and that the authenticated user has permission to create invoices for it.
- Invalid invoice data: Required fields like invoice number, dates, amount, and currency must be provided and correctly formatted.
- Authentication errors: Verify that the API key or OAuth2 credentials are valid and have sufficient permissions.
- API rate limits or network issues: If requests fail intermittently, check network connectivity and Qonto API usage limits.
- Error messages from Qonto API: These will usually indicate what field or parameter caused the failure; review the error message and adjust input accordingly.
Links and References
- Qonto API Documentation – Official API docs for detailed information on client invoices and other resources.
- n8n Documentation – For general guidance on using credentials and configuring nodes.