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 supplier invoices in bulk, including associating attachments with each invoice. It is useful for automating the process of submitting multiple supplier invoices to an organization's accounting system, especially when invoices come with supporting documents that need to be linked.
Typical use cases include:
- Uploading batches of supplier invoices received from vendors.
- Attaching scanned or digital copies of invoices as proof.
- Streamlining accounts payable workflows by programmatically creating invoices and linking their attachments.
For example, a finance team can use this node to automatically create supplier invoices after receiving them via email, attaching the scanned PDFs stored in the workflow.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API: either "Login and Secret-Key" or "OAuth2". |
| Organization ID | The unique identifier of the organization for which supplier invoices will be created. |
| Supplier Invoices | A collection of supplier invoice details to create. Each invoice includes: |
| - Invoice Number | Unique number identifying the supplier invoice. |
| - Invoice Date | Date when the supplier invoice was issued. |
| - Amount | Monetary amount of the supplier invoice. |
| - Currency | Currency code (e.g., EUR) of the invoice amount. |
| - Attachment IDs | Comma-separated string of attachment IDs associated with the invoice (linking supporting documents). |
Output
The node outputs an array of JSON objects representing the response from the Qonto API after creating the supplier invoices. Each object corresponds to a created supplier invoice and contains details such as invoice identifiers, status, and any metadata returned by the API.
No binary data output is produced by 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.
- The user must provide valid organization IDs and attachment IDs that exist in Qonto.
Troubleshooting
- Missing or invalid Organization ID: The API call will fail if the organization ID is not provided or incorrect. Ensure the correct organization identifier is used.
- Invalid Attachment IDs: If attachment IDs do not correspond to existing attachments in Qonto, the API may reject the request. Verify attachment existence before referencing.
- Authentication errors: Incorrect or expired credentials will cause authentication failures. Re-authenticate or update credentials as needed.
- API rate limits or network issues: Requests may fail due to rate limiting or connectivity problems. Implement retry logic or check network status.
- Malformed input data: Required fields like invoice number, date, amount, currency, and attachment IDs must be correctly formatted; otherwise, the API will return validation errors.
Links and References
- Qonto API Documentation
- n8n Documentation on Credentials
- UUID npm package (used internally for idempotency keys)