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 perform various operations on financial commands and related resources. Specifically, for the Financial > Commands resource with the Get Many operation, it retrieves multiple financial command records from the Kobana system.
Typical use cases include:
- Fetching a list of financial commands for reporting or reconciliation.
- Retrieving paginated or filtered sets of commands based on query parameters.
- Automating workflows that require bulk access to financial command data.
For example, a user might want to get all recent financial commands or limit the results to the latest 50 commands matching certain criteria.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available results or limit the number of returned items. |
| Limit | Maximum number of results to return when not returning all (minimum 1, maximum 100). |
| Additional Fields | JSON object containing extra fields to include in the request (optional). |
| Query Parameters | JSON object with additional query parameters to filter or modify the request (optional). |
Output
The node outputs an array of JSON objects representing the financial commands retrieved from the Kobana API. Each item corresponds to one financial command record with its associated data fields as provided by the API.
No binary data output is involved in this operation.
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 other external dependencies are required.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing malformed JSON in "Additional Fields" or "Query Parameters" may result in request errors.
- Exceeding the allowed limit (over 100) will be rejected by the API.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- JSON parsing errors suggest incorrect formatting in input fields; ensure valid JSON syntax.
- Rate limiting or quota exceeded errors may occur if too many requests are made; consider using "Return All" carefully or adding delays.
Links and References
- Kobana API Documentation (official API docs for detailed endpoint info)
- n8n documentation on HTTP Request Node for understanding request options and authentication setup