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 user information, specifically supporting the "Get Many" operation under the "V1 > User Info" resource. It allows users to fetch multiple user info records from Kobana, optionally controlling the number of results returned or applying query parameters to filter the data.
Common scenarios for this node include:
- Retrieving a list of user information records for reporting or auditing.
- Fetching user info in bulk for synchronization with other systems.
- Applying filters via query parameters to narrow down the user info results.
Example use case:
- A company wants to extract all user info records related to their account on Kobana to analyze user activity or export data for compliance purposes.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available user info records or limit the number of results returned. |
| Limit | Maximum number of user info records to return when "Return All" is false (1 to 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 (optional). |
Output
The node outputs an array of JSON objects representing user information records retrieved from the Kobana API. Each item corresponds to one user info record as returned by the API.
If the API supports binary data for this resource (not indicated here), it would be summarized accordingly, but for "User Info" the output is purely JSON data.
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 cause request errors.
- Exceeding API rate limits or requesting too many records without "Return All" enabled might result in partial data or errors.
Error messages:
- Authentication errors typically indicate invalid or missing API keys; verify and update credentials.
- JSON parsing errors suggest malformed JSON input in properties; ensure valid JSON syntax.
- API response errors may include HTTP status codes and messages; consult Kobana API documentation for details.
Links and References
- Kobana API Documentation (assumed official API docs)
- n8n documentation on HTTP Request Node for understanding API calls and authentication setup
