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 accounts and related resources. Specifically, for the Financial > Accounts resource with the Get operation, it retrieves detailed information about a specific financial account by its unique ID.
Typical use cases include:
- Fetching details of a particular financial account to display or process in workflows.
- Integrating Kobana financial account data into other systems or reports.
- Automating account verification or reconciliation processes by retrieving up-to-date account info.
Example: You have an account ID from a previous step or external source, and you want to get all associated details such as account name, balance, provider, or status to make decisions or trigger further actions.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the financial account to retrieve. This is a required string input. |
Output
The node outputs a JSON object representing the financial account's details as returned by the Kobana API. The structure typically includes fields such as account identifiers, names, balances, statuses, and related metadata depending on the API response.
No binary data output is produced by this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n, which provides authentication to access the Kobana API endpoints.
- The node dynamically selects the API base URL based on the environment (production or sandbox).
- Network connectivity to the Kobana API service is necessary.
Troubleshooting
- Invalid or missing ID: If the provided account ID is incorrect or not found, the API will return an error. Ensure the ID is valid and exists in your Kobana account.
- Authentication errors: If the API key or credentials are invalid or expired, requests will fail. Verify that the Kobana API credential is correctly set up and has proper permissions.
- API rate limits or downtime: Temporary failures may occur due to API limits or service issues. Implement retry logic or check Kobana service status if persistent errors happen.
- JSON parsing errors: When providing additional JSON inputs (not applicable here for Get), ensure the JSON syntax is correct to avoid parsing exceptions.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using Credentials
- n8n community forums for troubleshooting and examples