Kontoflux.io icon

Kontoflux.io

Access your Bank Accounts and Transactions with Kontoflux.io

Actions7

Overview

The "Search Transactions" operation in the Kontoflux.io node allows users to query their bank transactions using a specific search string and various filters. This operation is useful for retrieving transaction data that matches particular criteria, such as date ranges, categories, or account identifiers. It supports sorting and pagination, enabling efficient browsing through large sets of transaction records.

Practical examples include:

  • Searching for all transactions containing a specific keyword or description.
  • Filtering transactions within a certain date range or category.
  • Sorting transactions by amount or booking date.
  • Limiting results to a manageable number with offset support for pagination.

This operation is beneficial for financial analysis, auditing, or integrating transaction data into workflows.

Properties

Name Meaning
Search String Specific search string to match against the transactions (required).
Limit Maximum number of transactions to return (1 to 250).
Offset Offset for pagination to skip a number of transactions before starting to return results.
Options Collection of additional options:
  Sort Sort order of transactions: DESC (descending) or ASC (ascending).
  Sort By Field to sort transactions by: Creation Date, Amount, Booking Date, Import Date, or Value Date.
Filter Collection of filters to narrow down the search:
  Account IBAN or internal account ID to filter transactions by account.
  Category Exact category name or category ID to filter transactions.
  Parent Category Exact parent category name or ID to filter transactions.
  Valued before Filter transactions valued before this date/time.
  Valued after Filter transactions valued after this date/time.
  Booked before Filter transactions booked before this date/time.
  Booked after Filter transactions booked after this date/time.
  Imported before Filter transactions imported into Kontoflux before this date/time.
  Imported after Filter transactions imported into Kontoflux after this date/time.

Output

The output contains a JSON array of transaction objects matching the search criteria. Each transaction object typically includes details such as transaction ID, amount, booking date, value date, category, account information, and descriptive fields.

If binary data is returned (not indicated here), it would represent associated files or attachments related to transactions, but this operation primarily returns structured JSON data.

Dependencies

  • Requires an API key credential for Kontoflux.io with access to the workspace.
  • The node uses the Kontoflux.io REST API endpoint, dynamically constructed using the workspace ID from credentials.
  • Proper network connectivity to the Kontoflux.io API service is necessary.

Troubleshooting

  • Empty Results: If no transactions are returned, verify the search string and filters are correct and that transactions exist matching those criteria.
  • Invalid Credentials: Authentication errors indicate issues with the provided API key or workspace ID; ensure credentials are valid and have required permissions.
  • Pagination Issues: Using an offset beyond the available number of transactions will result in empty responses; adjust limit and offset accordingly.
  • Date Filters: Ensure date/time values are correctly formatted and logical (e.g., "valuedAfter" should not be after "valuedBefore").
  • API Rate Limits: Excessive requests may trigger rate limiting; implement retries or reduce request frequency.

Links and References

Discussion