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 administrative connections, specifically supporting the "Get Many" operation under the "Admin > Connections" resource. It allows users to retrieve multiple connection records from the Kobana system efficiently.
Typical use cases include:
- Fetching a list of all admin connections for auditing or monitoring purposes.
- Retrieving a subset of connections based on query parameters such as filters or pagination.
- Integrating Kobana connection data into workflows for reporting or synchronization.
For example, a user might want to get all active admin connections or limit the results to the first 50 connections for display in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return (applicable if "Return All" is false). |
| 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, sorting). |
Output
The node outputs an array of JSON objects representing the retrieved admin connections. Each item corresponds to one connection record returned by the Kobana API.
- The
jsonoutput field contains the connection data as received from the API. - 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 other external dependencies are required.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid JSON in "Additional Fields" or "Query Parameters" may result in request errors.
- Exceeding the maximum allowed limit (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 malformed JSON input; ensure proper JSON formatting.
- API rate limits or server errors should be handled by retrying after some delay or checking API status.
Links and References
- Kobana API Documentation (for detailed API endpoints and parameters)
- n8n documentation on HTTP Request Node (conceptual similarity)
