Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation retrieves the bank statement for a specific fund account. It is useful when you want to obtain detailed transaction records or statements related to a particular fund account within a financial system. Typical use cases include financial reconciliation, auditing, reporting, or monitoring cash flows associated with fund accounts.

For example, a user might want to fetch all transactions from a fund account over a certain date range or filter by specific criteria such as transaction type or amount.

Properties

Name Meaning
Account Id Identifier of the account. Specifies which account's fund account bank statement to retrieve.
Fund Account Id Identifier of the specific fund account whose bank statement is requested.
Filter JSON-stringified and URL-encoded filter expression object conforming to a bank statement filter schema. Allows filtering results by criteria such as date ranges or other attributes.
Skip Number of objects to skip from the beginning of the result set. Useful for pagination.
Take Maximum number of objects to return. Limits the size of the result set.
Order By JSON-stringified and URL-encoded sort expression object conforming to a bank statement order schema. Defines sorting order of the returned bank statement entries.

Output

The output contains a JSON array of bank statement entries corresponding to the specified fund account and filters. Each entry typically includes details such as transaction dates, amounts, descriptions, and other relevant banking information.

If the node supports binary data output (not explicitly indicated here), it would represent bank statement files or attachments in binary form, but this operation primarily returns structured JSON data.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external financial service.
  • The node depends on the external API endpoint that provides fund account bank statements.
  • Proper base URL configuration for the API is necessary.

Troubleshooting

  • Invalid or missing identifiers: Ensure that both "Account Id" and "Fund Account Id" are correctly provided; otherwise, the API call will fail.
  • Malformed filter or orderBy JSON: The filter and orderBy properties must be valid JSON strings and properly URL-encoded. Invalid JSON will cause errors.
  • Pagination issues: If using Skip and Take, ensure values are non-negative integers; otherwise, unexpected results or errors may occur.
  • Authentication errors: Verify that the API key or authentication credentials are correctly set up in n8n.
  • API rate limits or connectivity problems: Network issues or API limits can cause failures; check logs and retry accordingly.

Links and References

  • Refer to the external API documentation for the fund account bank statement endpoint for detailed schema and examples.
  • JSON Schema references for IBankStatementFilter and IBankStatementOrderBy to construct valid filter and order expressions.

Discussion