Actions34
- Banking Operation (India) Actions
- Catalog Operation Actions
- Contact Operation Actions
- HRMS Operation (India) Actions
- Purchase Operation (India) Actions
- Sales Operation (India) Actions
- Tax Operation (India) Actions
Overview
This node interacts with a banking API focused on Indian banking operations. Specifically, the Get Bank Statement operation allows users to retrieve bank account statements for a selected bank account within a specified date range.
Typical use cases include:
- Automating financial reconciliation by fetching bank statements directly into workflows.
- Integrating bank statement data with accounting or ERP systems.
- Generating reports or alerts based on transaction history from specific bank accounts.
For example, a user can select "ICICI Bank," choose a particular bank account linked to their profile, specify a date range (e.g., last month), and automatically fetch the statement data for further processing or analysis.
Properties
| Name | Meaning |
|---|---|
| Select Bank | Choose the bank from which to fetch the statement. Options: "Select Bank", "ICICI Bank", "Axis Bank". |
| Bank Account Name or ID | Select the specific bank account by name or ID. The list is dynamically loaded from the API. This is required. |
| From Date | Start date for the bank statement period in DD-MM-YYYY format. Required. |
| To Date | End date for the bank statement period in DD-MM-YYYY format. Required. |
Output
The node outputs JSON data representing the bank statement details for the selected account and date range. The exact structure depends on the API response but typically includes transaction records such as dates, descriptions, amounts, balances, and other relevant metadata.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential and authentication token to access the banking API.
- The node performs login requests to obtain an API token before making subsequent calls.
- The API base URL and credentials (email, password, API key) must be configured in n8n credentials.
- The node uses dynamic option loading methods to populate bank accounts based on the selected bank.
Troubleshooting
- Authentication failures: If the node cannot log in, it will throw errors indicating failed authentication. Verify that the API key, email, and password credentials are correct.
- No active bank accounts found: If no linked or active bank accounts exist for the selected bank, the node returns a message indicating this. Ensure the bank account is active and linked properly.
- Invalid date ranges: The
fromDateandtoDatefields are required; missing or incorrectly formatted dates may cause errors. - API connectivity issues: Network problems or incorrect API URLs can cause request failures. Confirm the API endpoint is reachable and correctly configured.
Links and References
- n8n Expressions Documentation — for using expressions in input fields.
- No direct external API documentation links were found in the source code; consult your banking API provider for detailed API specs.