Overview
This node interacts with the SePay API to retrieve transaction data. Specifically, the "Transaction" resource with the "Get All" operation allows users to fetch multiple transactions from their SePay account. It supports filtering by various criteria such as account number, date range, reference number, and amounts, enabling targeted queries.
Common scenarios include:
- Retrieving all recent transactions for reconciliation or reporting.
- Filtering transactions within a specific date range or by account number.
- Limiting the number of transactions returned for performance or pagination purposes.
Practical example:
A finance team wants to extract all transactions from the last month for a particular bank account to generate monthly financial reports. They can use this node to specify the account number and date filters, returning only relevant transactions.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching transactions or limit the results. |
| Limit | Maximum number of transactions to return if not returning all (minimum 1, maximum 5000). |
| Filters | Collection of optional filters to narrow down the transactions: |
| - Account Number | Filter transactions by bank account number. |
| - Transaction Date Min | Show transactions created on or after this date/time (format: YYYY-MM-DD HH:MM:SS). |
| - Transaction Date Max | Show transactions created on or before this date/time (format: YYYY-MM-DD HH:MM:SS). |
| - Since ID | Show transactions starting from this transaction ID onwards. |
| - Reference Number | Filter transactions by reference number. |
| - Amount In | Filter transactions by incoming amount. |
| - Amount Out | Filter transactions by outgoing amount. |
Output
The node outputs an array of transaction objects in the json output field. Each transaction object contains details as provided by the SePay API under the /transactions/list endpoint. The exact structure depends on the API response but typically includes fields like transaction ID, account number, date, amounts, reference numbers, and other transaction metadata.
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 the Axios HTTP client internally to make REST API calls to
https://my.sepay.vn/userapi.
Troubleshooting
- API Authentication Errors: If the API token is invalid or missing, the node will throw an error indicating an authorization failure. Ensure the API key credential is correctly set up.
- Invalid Filter Values: Providing incorrectly formatted dates or unsupported filter values may result in no data returned or API errors. Use the specified date format (
YYYY-MM-DD HH:MM:SS) and valid strings. - Limit Exceeded: Setting the limit above 5000 will be rejected; keep it within the allowed range.
- Network Issues: Connectivity problems to the SePay API endpoint will cause request failures. Verify network access and API availability.
- API Error Messages: The node surfaces errors returned by the SePay API prefixed with "SePay API Error:". Review the message for details and adjust parameters accordingly.
Links and References
- SePay API Documentation (Assumed URL based on API base URL, verify actual docs)
- Axios HTTP Client
- n8n Documentation - Creating Nodes