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 to manage administrative users and other resources. Specifically, for the Admin > Users resource with the Get Many operation, it retrieves multiple admin user records from the Kobana system. This is useful in scenarios where you need to list or audit all admin users, synchronize user data, or perform bulk operations based on user information.
Practical examples include:
- Fetching all admin users to display in a dashboard.
- Retrieving a limited set of users for reporting or monitoring purposes.
- Applying query filters to find users matching specific criteria.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return (used 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., search criteria). |
Output
The output is a JSON array where each element represents an admin user object retrieved from the Kobana API. Each object contains the user details as provided by the API response.
If the node is configured to return all results, the output includes all matching users; otherwise, it returns up to the specified limit.
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 are required beyond the Kobana API access.
Troubleshooting
Common issues:
- Authentication errors due to missing or invalid API credentials.
- Exceeding API rate limits when requesting large datasets without pagination.
- Malformed JSON in "Additional Fields" or "Query Parameters" causing request failures.
Error messages:
- Errors returned from the Kobana API will be included in the output if "Continue On Fail" is enabled.
- Typical error messages may relate to invalid parameters, unauthorized access, or resource not found.
Resolutions:
- Verify that the API key credential is correctly configured and has necessary permissions.
- Use the "Limit" property to restrict the number of results and avoid timeouts.
- Ensure JSON inputs for additional fields and query parameters are valid and properly formatted.
Links and References
- Kobana API Documentation (official API docs for detailed endpoint info)
- n8n documentation on Using Credentials
- n8n documentation on HTTP Request Node for understanding API calls
