Actions42
- Attachment Actions
- Payment Actions
- Transaction Actions
- Request Inquiry Actions
- Card Actions
- bunq.me Actions
- Webhook Actions
- Scheduled Payment Actions
- Export/Statement Actions
- User Actions
- Monetary Account Actions
Overview
The node interacts with the bunq banking API to perform operations related to bank transactions. Specifically, for the Transaction - Get operation, it retrieves detailed information about a specific transaction from a monetary account. This is useful when you want to fetch details of a particular payment or transaction by its unique ID.
Common scenarios include:
- Fetching transaction details for reconciliation or auditing.
- Retrieving transaction metadata for reporting or notification purposes.
- Integrating transaction data into other workflows or systems.
Example: You have a monetary account and want to get details about a specific payment made or received by providing the transaction ID.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user. Leave empty to use the current authenticated user. |
| Account ID | The ID of the monetary account from which to retrieve the transaction. (Required) |
| Transaction ID | The unique ID of the transaction to retrieve details for. (Required) |
Output
The output is a JSON object representing the detailed information of the requested transaction. It includes all relevant fields returned by the bunq API for that transaction, such as amount, currency, description, status, timestamps, and counterparty details.
No binary data is output for this operation.
Dependencies
- Requires access to the bunq banking API.
- Requires an API key credential or OAuth2 token configured in n8n to authenticate requests to the bunq API.
- The node uses internal helper functions to format the API response into a simplified structure.
Troubleshooting
- Missing or invalid Account ID or Transaction ID: The node requires these IDs to be provided; otherwise, the API call will fail. Ensure these are correctly set.
- Authentication errors: If the API credentials are missing or invalid, the request will fail. Verify your API key or OAuth2 credentials.
- Transaction not found: If the transaction ID does not exist under the specified account, the API will return an error. Double-check the IDs.
- API rate limits or connectivity issues: Network problems or API limits may cause failures. Retry or check network connectivity.