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 Transaction resource with the Get One operation, it retrieves a single transaction by its unique ID. This is useful in scenarios where you need detailed information about a specific transaction from your Qonto account, such as for reconciliation, auditing, or displaying transaction details in an application.
Practical examples include:
- Fetching details of a particular bank transaction to verify payment status.
- Retrieving transaction metadata for reporting or bookkeeping purposes.
- Accessing transaction data to trigger downstream workflows based on transaction attributes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate requests. Options: API Key |
| ID | The unique identifier of the transaction to retrieve. Required for the Get One operation |
Output
The node outputs JSON data representing the retrieved transaction object. This JSON contains all relevant fields returned by the Qonto API for a single transaction, such as amount, date, description, status, and any associated metadata.
If the node encounters an error (e.g., invalid ID), the output JSON will contain an error field with the error message.
The node does not output binary data.
Dependencies
- Requires a valid API key credential for authenticating with the Qonto API.
- The node uses the Qonto API endpoints, switching between sandbox and production environments based on configuration.
- Network connectivity to Qonto's API servers is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent transaction ID will result in an error.
- Missing or incorrect API key authentication will cause authorization failures.
- Network timeouts or connectivity issues can prevent successful API calls.
Error messages:
"Unknown resource: transaction"— indicates the resource parameter was not recognized; ensure "transaction" is selected.- Errors returned from the Qonto API (e.g., 404 Not Found) will be passed through in the output's
errorfield.
Resolutions:
- Verify the transaction ID is correct and exists in your Qonto account.
- Confirm that the API key credential is properly configured and has sufficient permissions.
- Check network connectivity and firewall settings to allow outbound requests to Qonto.