Kontoflux.io icon

Kontoflux.io

Access your Bank Accounts and Transactions with Kontoflux.io

Actions7

Overview

The node "Kontoflux.io" provides access to bank accounts and transactions via the Kontoflux.io API. Specifically, for the Transactions resource with the Get Transaction by Identifier operation, it retrieves detailed information about a single transaction using its unique transaction ID. This is useful when you want to fetch precise data about a specific transaction from your bank account history.

Practical examples include:

  • Fetching details of a particular payment or deposit by its transaction ID.
  • Verifying transaction information before processing refunds or reconciliations.
  • Displaying transaction details in custom dashboards or reports.

Properties

Name Meaning
Transaction ID The unique numeric identifier of the transaction you want to retrieve. This property is required.

Output

The node outputs JSON data representing the details of the requested transaction. This typically includes fields such as transaction amount, date, description, category, and other metadata related to the transaction.

If the node supports binary data output (not indicated here), it would represent any associated files or attachments linked to the transaction, but this is not evident from the provided code.

Dependencies

  • Requires an active connection to the Kontoflux.io API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for API requests is dynamically constructed using a workspace identifier from credentials.
  • The node expects JSON responses from the API.

Troubleshooting

  • Missing or invalid Transaction ID: Ensure that the Transaction ID is provided and is a valid number; otherwise, the API call will fail.
  • Authentication errors: Verify that the API key or authentication token is correctly set up in n8n credentials.
  • Network or API errors: Check internet connectivity and confirm that the Kontoflux.io service is operational.
  • Incorrect workspace ID: Since the base URL depends on a workspace ID, ensure this value is correctly configured in credentials.

Common error messages might include unauthorized access, resource not found (if the transaction ID does not exist), or bad request due to invalid parameters.

Links and References

Discussion