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
This node integrates with the Qonto API to retrieve data related to various financial resources. Specifically, for the Supplier Invoice resource with the Get One operation, it fetches a single supplier invoice by its unique ID. This is useful in scenarios where you need detailed information about a specific supplier invoice, such as verifying invoice details, checking payment status, or integrating invoice data into other workflows like accounting or reporting.
Practical examples:
- Automatically retrieving a supplier invoice after receiving a notification to process payments.
- Fetching invoice details to cross-check with purchase orders or inventory systems.
- Using the invoice data to generate reports or trigger further automation steps based on invoice status.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Options: API Key |
| ID | The unique identifier of the supplier invoice to retrieve. This is a required string. |
Output
The node outputs an array of JSON objects representing the retrieved supplier invoice(s). Each JSON object contains all the fields returned by the Qonto API for that supplier invoice, such as invoice number, date, amount, supplier details, status, and any other metadata provided by Qonto.
If the node supports binary data (not explicitly shown here), it would typically represent attachments or documents related to the invoice, but this is not indicated in the provided code snippet.
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 setting (sandbox or production).
- Network connectivity to Qonto's endpoints.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Providing an incorrect or non-existent invoice ID will result in errors or empty responses.
- Network timeouts or connectivity issues can prevent successful API calls.
Error messages:
"Unknown resource: supplierInvoice"— indicates the resource name was not recognized; ensure the resource parameter is correctly set.- API error messages from Qonto (e.g., unauthorized, not found) will be propagated; verify credentials and input parameters.
Resolutions:
- Double-check the API key and ensure it has the necessary permissions.
- Verify the invoice ID exists in your Qonto account.
- Ensure the node’s environment setting matches the intended Qonto environment (sandbox vs production).
Links and References
- Qonto API Documentation
- n8n documentation on creating custom nodes
