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 statement transactions and other related financial resources. Specifically, for the Financial > Statement Transactions resource with the Get operation, it retrieves detailed information about a specific financial statement transaction by its unique ID.
This node is beneficial in scenarios where you need to programmatically access transaction details from your financial statements, such as reconciling accounts, auditing transactions, or integrating financial data into other systems for reporting or analysis.
Practical example:
You have an automated workflow that processes bank statement transactions daily. Using this node, you can fetch detailed information about each transaction by its ID to verify amounts, dates, and descriptions before further processing or storing them in your database.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the financial statement transaction to retrieve. This property is required for the "Get" operation. |
Output
The node outputs a JSON object representing the financial statement transaction retrieved from the Kobana API. The structure typically includes all relevant transaction details such as transaction date, amount, description, account information, and status.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the transaction, but this is not applicable for the "Get" operation on statement transactions.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- No additional external dependencies are needed beyond the Kobana API access.
Troubleshooting
Common issues:
- Invalid or missing ID parameter will cause the API request to fail.
- Authentication errors if the API key credential is incorrect or expired.
- Network connectivity issues preventing access to the Kobana API endpoints.
Error messages:
"Resource not found": The provided ID does not correspond to any existing statement transaction. Verify the ID value."Unauthorized"or"Authentication failed": Check that the API key credential is correctly configured and has necessary permissions."Request timeout"or"Network error": Ensure stable internet connection and that the Kobana API service is reachable.
Resolving these usually involves verifying input parameters, refreshing credentials, and checking network status.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using API Credentials
