Actions215
- V1 > Bank Billets Actions
- V1 > Bank Billet Accounts Actions
- V1 > Bank Billet Batches Actions
- V1 > Bank Billet Batch Exports Actions
- V1 > Bank Billet Discharges Actions
- V1 > Bank Billet Payments Actions
- V1 > Bank Billet Registrations Actions
- V1 > Bank Billet Remittances Actions
- V1 > Customers Actions
- V1 > Customer Subscriptions Actions
- V1 > Discharges Actions
- V1 > Email Deliveries Actions
- V1 > Events Actions
- V1 > Imports Actions
- V1 > Installments Actions
- V1 > Remittances Actions
- V1 > Reports Actions
- V1 > SMS Deliveries Actions
- V1 > User Info Actions
- V1 > Webhook Deliveries Actions
- V1 > Webhooks Actions
- Admin > Users Actions
- Admin > Connections Actions
- Admin > Certificates Actions
- Admin > Subaccounts Actions
- Charge > PIX Actions
- Charge > PIX Accounts Actions
- Data > Bank Billet Queries Actions
- EDI > EDI Boxes Actions
- Financial > Accounts Actions
- Financial > Balances Actions
- Financial > Commands Actions
- Financial > Statement Transactions Actions
- Financial > Transaction Imports Actions
- Financial > Providers Actions
- Payment > Bank Billets Actions
- Payment > Bank Billet Batches Actions
- Payment > Batches Actions
- Payment > DARFs Actions
- Payment > DARF Batches Actions
- Payment > PIX Actions
- Payment > PIX Batches Actions
- Payment > Utilities Actions
- Payment > Utility Batches Actions
- Transfer > Batches Actions
- Transfer > Internal Actions
- Transfer > Internal Batches Actions
- Transfer > PIX Actions
- Transfer > PIX Batches Actions
- Transfer > TED Actions
- Transfer > TED Batches Actions
Overview
This node integrates with the Kobana API to manage financial account balances. Specifically, the Financial > Balances resource with the Get operation allows users to retrieve detailed information about a specific account balance by its unique ID.
Typical use cases include:
- Fetching the current balance details of a financial account for reporting or reconciliation.
- Integrating balance data into workflows that require up-to-date financial status.
- Automating financial monitoring and alerting based on balance thresholds.
For example, a user might configure this node to get the balance of a particular account before initiating a payment or transfer, ensuring sufficient funds are available.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the financial balance resource to retrieve. This is required to specify which balance record to fetch. |
Output
The node outputs JSON data representing the financial balance details retrieved from the Kobana API. The structure typically includes fields such as balance amount, currency, account identifiers, timestamps, and other metadata related to the balance.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Kobana API via an API key credential configured in n8n.
- The node dynamically selects the API environment URL based on the credential's environment setting (production or sandbox).
- No additional external dependencies beyond the Kobana API and proper authentication.
Troubleshooting
Common issues:
- Invalid or missing ID property will cause the request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Resource not found": The specified ID does not exist; verify the ID value."Unauthorized"or"Authentication failed": Check that the API key credential is valid and has necessary permissions."Request timeout"or"Network error": Ensure network access to the Kobana API endpoints.
To resolve these, confirm the correctness of the input ID, validate API credentials, and check network connectivity.
Links and References
- Kobana API Documentation (official API docs for detailed resource and operation info)
- n8n documentation on API Credentials for setting up the required authentication token