Kontoflux.io icon

Kontoflux.io

Access your Bank Accounts and Transactions with Kontoflux.io

Actions7

Overview

The "Get All Transactions" operation in the Kontoflux.io node retrieves multiple bank transactions from your connected accounts. It is useful for scenarios where you want to fetch a list of transactions for analysis, reporting, reconciliation, or further processing within an automation workflow.

Typical use cases include:

  • Downloading recent transactions for bookkeeping or accounting.
  • Filtering transactions by date ranges, categories, or accounts.
  • Paginating through large sets of transaction data.
  • Sorting transactions by amount, booking date, or creation date.

For example, you could use this node to get all transactions booked after a certain date and sort them by amount in descending order to identify the largest expenses.

Properties

Name Meaning
Return All Whether to return all matching transactions or limit the number of results. If false, the number of transactions returned is limited by the "Limit" property.
Limit Maximum number of transactions to return when "Return All" is false. Value must be between 1 and 250.
Offset Pagination offset to skip a number of transactions before starting to return results. Used when "Return All" is false.
Options Additional options to customize the query:
  Sort Sort order of the transactions. Possible values: "DESC" (descending), "ASC" (ascending). Default is "DESC".
  Sort By Field to sort transactions by. Possible values: "Creation Date", "Amount", "Booking Date", "Import Date", "Value Date". Default is "Creation Date".
Filter Filters to narrow down the transactions returned:
  Account Filter transactions by account IBAN or internal account ID.
  Category Filter transactions by exact category name or category ID.
  Parent Category Filter transactions by exact parent category name or ID.
  Valued Before Filter transactions valued before a specific date/time.
  Valued After Filter transactions valued after a specific date/time.
  Booked Before Filter transactions booked before a specific date/time.
  Booked After Filter transactions booked after a specific date/time.
  Imported Before Filter transactions imported into Kontoflux before a specific date/time.
  Imported After Filter transactions imported into Kontoflux after a specific date/time.

Output

The node outputs an array of transaction objects in the json field of the output data. Each transaction object typically contains details such as:

  • Transaction ID
  • Amount
  • Booking date
  • Value date
  • Import date
  • Account information
  • Category and parent category
  • Other metadata related to the transaction

This structured JSON output can be used downstream in workflows for further processing, filtering, or integration with other systems.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to transactions, but this operation focuses on JSON transaction data.

Dependencies

  • Requires an active API key credential for Kontoflux.io with access to the workspace containing the bank accounts and transactions.
  • The node communicates with the Kontoflux.io REST API endpoint at https://api.kontoflux.io/v1/.
  • Proper configuration of the workspace ID in credentials is necessary for correct API base URL construction.

Troubleshooting

  • No transactions returned: Check that the filters are not too restrictive and that the account and date ranges are correct.
  • API authentication errors: Ensure the API key credential is valid and has the required permissions.
  • Pagination issues: When using pagination, verify that the "Offset" and "Limit" values are set correctly and that "Return All" is false if you want to paginate.
  • Invalid filter values: Dates should be in proper ISO format; invalid dates may cause errors or empty results.
  • Sorting not applied: Confirm that the "Sort" and "Sort By" options are set correctly; defaults apply if omitted.

Links and References

Discussion