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 interacts with the Qonto API to retrieve detailed information about a specific bank transaction. It is designed to fetch a single transaction by its unique identifier within a particular bank account. This functionality is useful in scenarios where you need to verify, audit, or process individual transactions programmatically, such as reconciling payments, tracking expenses, or integrating transaction data into other financial systems.
For example, you might use this node to:
- Retrieve details of a payment made on a certain date for accounting purposes.
- Fetch transaction metadata to trigger follow-up workflows based on transaction status or amount.
- Integrate transaction data into a CRM or ERP system for enhanced financial reporting.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with the Qonto API. Options: "Login and Secret-Key", "OAuth2". |
| ID | The unique identifier of the transaction to retrieve. Required to specify which transaction to show. |
Output
The node outputs a JSON object representing the detailed data of the requested transaction. This includes all relevant fields returned by the Qonto API for a single transaction, such as amounts, dates, references, statuses, and related metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Qonto API.
- Requires either an API key credential (Login and Secret-Key) or OAuth2 authentication configured in n8n.
- No additional environment variables are explicitly required beyond standard API credentials.
Troubleshooting
Common issues:
- Invalid or missing transaction ID will cause the API request to fail.
- Authentication errors if the provided credentials are incorrect or expired.
- Network connectivity issues may prevent reaching the Qonto API endpoint.
Error messages and resolutions:
- "Transaction not found": Verify that the transaction ID is correct and exists in the specified bank account.
- "Unauthorized" or "Authentication failed": Check that the API credentials are valid and have sufficient permissions.
- Timeout or network errors: Ensure stable internet connection and that the Qonto API service is reachable.
Links and References
- Qonto API Documentation – Official API docs for detailed transaction data structure and authentication methods.