Actions7
- Accounts Actions
- Transactions Actions
- Categories Actions
Overview
The Kontoflux.io node provides access to bank accounts and transactions via the Kontoflux.io API. Specifically, the "Get Account by Identifier" operation under the "Accounts" resource allows users to retrieve detailed information about a single bank account using an identifier such as an IBAN or an internal ID. This is useful for scenarios where you need to fetch specific account details for reporting, reconciliation, or integration with other financial systems.
Practical examples include:
- Retrieving account balance and metadata before processing transactions.
- Validating account information during onboarding or data synchronization.
- Fetching account details dynamically based on user input or workflow conditions.
Properties
| Name | Meaning |
|---|---|
| Account Identifier | The unique identifier of the account to retrieve. Can be an IBAN (e.g., DE123456781234) or an internal ID. This field supports searching and loading options dynamically from existing accounts. |
Output
The node outputs JSON data representing the details of the requested bank account. This typically includes fields such as account number, IBAN, account holder name, balance, currency, and other relevant metadata provided by the Kontoflux.io API.
If the node supports binary data output, it would generally relate to documents or statements associated with the account, but this is not indicated in the provided code snippet.
Dependencies
- Requires an active Kontoflux.io API key credential configured in n8n.
- The node uses the workspace ID from credentials to construct the base URL for API requests.
- Internet connectivity to reach the Kontoflux.io API endpoint (
https://api.kontoflux.io/v1/).
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect or non-existent account identifier will result in errors or empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid API keys or missing workspace ID.
- "Account not found" or similar messages suggest the provided identifier does not match any account.
Resolutions:
- Verify that the API key and workspace ID are correctly set up in n8n credentials.
- Double-check the account identifier format and existence.
- Ensure stable internet connection and that the Kontoflux.io service is operational.
Links and References
- Kontoflux.io API Documentation (hypothetical link for reference)
- n8n documentation on creating custom nodes