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, providing quick access to a wide range of operations related to financial and billing management. The "Get Many" operation under the "Default" resource allows users to retrieve multiple records (e.g., bank slips, customers, subscriptions, webhooks) from Kobana in a single request. This is useful for scenarios where you need to list or process batches of data, such as fetching all bank slips for reconciliation, listing customers for marketing campaigns, or retrieving subscriptions for billing analysis.
Practical examples include:
- Retrieving all bank slips issued within a date range to generate reports.
- Listing customers with specific query parameters for segmentation.
- Fetching all active subscriptions to monitor recurring revenue.
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 "Return All" is false (minimum 1, maximum 100). |
| Additional Fields | JSON object containing extra fields to include in the request, allowing customization. |
| Query Parameters | JSON object with additional query parameters to filter or modify the list request. |
Output
The node outputs a JSON array where each element corresponds to an item retrieved from Kobana based on the query. The structure of each item depends on the resource being queried but generally includes all relevant fields returned by the Kobana API for that resource.
If the node supports binary data output (not indicated for this operation), it would typically represent files or attachments related to the resource; however, for the "Get Many" operation, output is purely JSON data representing multiple records.
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 required beyond the Kobana API access.
Troubleshooting
Common Issues:
- Exceeding API rate limits when requesting large datasets without pagination.
- Incorrectly formatted JSON in "Additional Fields" or "Query Parameters" causing request failures.
- Missing or invalid API credentials leading to authentication errors.
Error Messages:
- Authentication errors: Ensure the API key credential is correctly configured and valid.
- JSON parse errors: Verify that JSON inputs for additional fields and query parameters are well-formed.
- Request limit errors: Use the "Limit" property to restrict the number of results or enable "Return All" cautiously.
Links and References
- Kobana API Documentation (official API docs)
- n8n documentation on HTTP Request node for understanding API calls
- General guidance on JSON formatting
