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 provides integration with the Qonto API, allowing users to interact with various Qonto resources. Specifically, for the Statement resource with the Get One operation, it retrieves a single statement by its unique ID. This is useful in scenarios where you need detailed information about a specific bank statement from Qonto, such as for reconciliation, auditing, or financial reporting.
Practical examples include:
- Fetching a particular bank statement to verify transaction details.
- Retrieving statement data to automate bookkeeping processes.
- Accessing statement metadata for compliance checks.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Options: API Key |
| ID | The unique identifier of the statement resource to retrieve. Must be provided as a string. |
Output
The node outputs JSON data representing the requested statement object retrieved from the Qonto API. The structure typically includes all relevant fields of a bank statement such as statement ID, date, balance, transactions summary, and other metadata.
If the node supports binary data output (not explicitly shown here), it would represent downloadable content related to the statement, such as PDF files of the statement document. However, based on the provided code and properties, the primary output is JSON-formatted statement data.
Dependencies
- Requires an active Qonto account with API access.
- Needs an API key credential configured in n8n for authentication.
- Network access to Qonto's API endpoints (
https://thirdparty.qonto.comor sandbox equivalent). - No additional external dependencies beyond the Qonto API and n8n environment.
Troubleshooting
- Common issues:
- Invalid or missing statement ID will cause errors when retrieving the resource.
- Incorrect or expired API key will result in authentication failures.
- Network connectivity problems can prevent successful API calls.
- Error messages:
"Unknown resource: statement"— indicates the resource name was not recognized; ensure "statement" is selected correctly.- API errors returned from Qonto (e.g., 404 Not Found if the statement ID does not exist) will be surfaced as error messages.
- Resolutions:
- Verify the statement ID is correct and exists in your Qonto account.
- Confirm the API key is valid and has necessary permissions.
- Check network settings and proxy configurations if applicable.
Links and References
- Qonto API Documentation — official reference for available endpoints and data structures.
- n8n Documentation — for general guidance on using credentials and configuring nodes.