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 retrieve multiple bank billet registrations (bank slip registrations) in bulk. Specifically, the "Get Many" operation under the "V1 > Bank Billet Registrations" resource allows users to fetch a list of bank billet registration records, optionally filtered or limited by query parameters.
Common scenarios where this node is beneficial include:
- Retrieving a batch of bank billet registrations for reporting or reconciliation.
- Fetching recent or filtered bank billet registrations based on custom query parameters.
- Integrating Kobana bank billet data into other workflows or systems for further processing.
For example, a user might want to get all bank billet registrations created within a certain date range or only the first 50 records for quick analysis.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return when not returning all (minimum 1, maximum 100). |
| Additional Fields | JSON object with additional fields for the request (optional extra parameters). |
| Query Parameters | JSON object with query parameters to filter or modify the request (e.g., filtering criteria). |
Note: The "Return All" and "Limit" properties control pagination behavior. If "Return All" is true, all matching records are fetched; otherwise, only up to "Limit" records are returned.
Output
The output is a JSON array where each element represents a bank billet registration record retrieved from the Kobana API. Each record contains the data fields as provided by the API response for bank billet registrations.
No binary data output is produced by 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 additional external dependencies beyond the Kobana API and its authentication.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid JSON in "Additional Fields" or "Query Parameters" may cause request errors.
- Exceeding the maximum allowed "Limit" (100) will likely result in validation errors.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid or missing API keys.
- JSON parsing errors suggest malformed JSON input in the properties.
- API rate limiting or quota exceeded errors may occur if too many requests are made in a short time.
Resolutions:
- Verify that the API key credential is correctly configured and has necessary permissions.
- Ensure JSON inputs are valid and properly formatted.
- Adjust "Limit" to be within allowed bounds.
- Check network connectivity and retry after some time if rate limits are hit.
Links and References
- Kobana API Documentation (general reference for API endpoints and usage)
- n8n documentation on Using Credentials
- n8n documentation on HTTP Request Node (for understanding API calls)
If you need details on other operations or resources, feel free to ask!
