SePay icon

SePay

Interact with SePay API

Actions3

Overview

This node interacts with the SePay API to perform operations on financial transactions. Specifically, for the Transaction resource and the Count operation, it counts the number of transactions that match specified filter criteria.

Common scenarios where this node is useful include:

  • Quickly determining how many transactions meet certain conditions without retrieving full transaction details.
  • Generating reports or dashboards that display transaction counts filtered by date ranges, account numbers, or other attributes.
  • Monitoring transaction volumes over time or for specific accounts.

For example, you could use this node to count all transactions for a particular bank account within a given date range, helping to analyze account activity or detect unusual patterns.

Properties

Name Meaning
Filters A collection of optional filters to narrow down which transactions are counted. Available filters:
• Account Number: Filter by bank account number.
• Transaction Date Min: Show transactions created after or equal to this date (format: YYYY-MM-DD HH:MM:SS).
• Transaction Date Max: Show transactions created before or equal to this date (format: YYYY-MM-DD HH:MM:SS).
• Since ID: Show transactions from this ID onwards (inclusive).

Note: Some filters like Reference Number, Amount In, and Amount Out exist but are only applicable to other operations (e.g., "Get All") and not to the Count operation.

Output

The output is a JSON array containing one or more objects with the following structure:

{
  "count": <number>
}
  • count: The total number of transactions matching the provided filters.

No binary data is output by this node.

Dependencies

  • Requires an active connection to the SePay API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • Uses HTTP GET requests to the SePay API endpoints:
    • /transactions/count with query parameters based on filters.

Troubleshooting

  • API Errors: If the SePay API returns an error, the node throws an error message prefixed with "SePay API Error:" followed by the API's error message. This usually indicates issues such as invalid credentials, malformed filters, or server-side problems.
    • Resolution: Verify that the API token is correct and has necessary permissions. Check filter values for correctness and format.
  • Empty or Missing Counts: If no transactions match the filters, the count will be zero. Ensure filters are set correctly and correspond to existing data.
  • Network Issues: Connectivity problems can cause request failures.
    • Resolution: Confirm network access to the SePay API endpoint and retry.

Links and References

Discussion