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 interacts with the Kobana API to manage Bank Billet Accounts (billing wallets) under the V1 API version. Specifically, the Get Many operation retrieves multiple billing wallet records from the Kobana system.
Use cases include:
- Fetching a list of billing wallets associated with your account for reporting or synchronization.
- Retrieving filtered or paginated sets of billing wallets based on query parameters.
- Integrating billing wallet data into workflows that require bulk processing or analysis.
For example, you might use this operation to get all billing wallets to display in a dashboard or to sync them with another financial system.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all billing wallet results or limit the number returned. |
| Limit | Maximum number of billing wallets to return if not returning all (minimum 1, maximum 100). |
| Additional Fields | JSON object with additional fields to include in the request (optional). |
| Query Parameters | JSON object with query parameters to filter or modify the request (e.g., filtering, sorting). |
Output
The output is a JSON array where each element represents a billing wallet object retrieved from the Kobana API. Each object contains the details of a billing wallet such as its ID, name, status, and other relevant metadata as provided by the API.
No binary data is output by this operation.
Dependencies
- Requires an active Kobana API credential with appropriate permissions.
- The node uses the Kobana API endpoint, switching between production and sandbox environments based on the credential environment setting.
- No additional external dependencies are required beyond the Kobana API access.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Exceeding API rate limits may result in errors or throttling.
- Providing malformed JSON in "Additional Fields" or "Query Parameters" can cause request errors.
- Requesting more than 100 items without enabling "Return All" will be limited by the API.
Error messages:
- Authentication errors: Check that the API key or token is valid and has correct permissions.
- JSON parse errors: Ensure that any JSON input fields are correctly formatted.
- API response errors: Review the error message returned by the API for specific causes (e.g., invalid parameters).
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n Documentation on Using Credentials
- n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)
