Kontoflux.io icon

Kontoflux.io

Access your Bank Accounts and Transactions with Kontoflux.io

Actions7

Overview

The "Match Transactions" operation in the Kontoflux.io node allows users to search for specific bank transactions by providing a search string and optional filters. This operation is useful when you want to find transactions that match certain criteria, such as a keyword in the transaction description, date ranges, account identifiers, or categories.

Typical use cases include:

  • Finding all transactions related to a particular vendor or merchant by searching with their name.
  • Filtering transactions within a specific date range or category.
  • Paginating through large sets of transactions using limit and offset parameters.

For example, you could search for all transactions containing the word "Amazon" that were booked after January 1, 2024, and limit the results to 100 entries.

Properties

Name Meaning
Search String Specific search string to match against the transactions. This is required and forms the core query for matching transactions.
Limit Maximum number of transactions to return. Accepts values from 1 to 250. Defaults to 250. Useful for controlling pagination size.
Offset Offset for pagination, allowing you to skip a number of transactions before starting to return results. Defaults to 0.
Filter A collection of optional filters to narrow down the search results:
  Account IBAN or internal account ID to filter transactions by a specific account.
  Category Exact category name or category ID to filter transactions by category.
  Parent Category Exact parent category name or ID to filter transactions by a parent category.
  Valued before Filter transactions valued before a given date/time.
  Valued after Filter transactions valued after a given date/time.
  Booked before Filter transactions booked before a given date/time.
  Booked after Filter transactions booked after a given date/time.
  Imported before Filter transactions imported into Kontoflux before a given date/time.
  Imported after Filter transactions imported into Kontoflux after a given date/time.

Output

The output of this operation is a JSON array of matched transactions. Each transaction object typically contains details such as transaction ID, amount, date (valued and booked), account information, category, description, and other metadata relevant to the transaction.

If the node supports binary data output (not explicitly indicated here), it would represent associated files or attachments related to transactions, but this operation primarily returns structured JSON data about transactions.

Dependencies

  • Requires an API key credential for Kontoflux.io workspace authentication.
  • The base URL for API requests is dynamically constructed using the workspace ID from credentials.
  • The node depends on Kontoflux.io's REST API endpoints for accounts, transactions, and categories.
  • Proper configuration of the API key and workspace ID in n8n credentials is necessary.

Troubleshooting

  • Empty Results: If no transactions are returned, verify that the search string and filters are correct and that there are matching transactions in the specified account or category.
  • Invalid Date Filters: Ensure date/time filters are in the correct ISO format. Incorrect formats may cause the API to reject the request.
  • API Authentication Errors: Check that the API key credential is valid and has access to the specified workspace.
  • Pagination Issues: When using limit and offset, ensure that offset does not exceed the total number of available transactions.
  • Rate Limits: Kontoflux.io API may enforce rate limits; if you encounter errors related to too many requests, consider adding delays or reducing request frequency.

Links and References

Discussion