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 enables interaction with the Kobana API, specifically allowing management of subaccounts under the Admin resource. The "Create" operation for Admin > Subaccounts lets users create new subaccounts by sending a JSON request body to the Kobana API.
Typical use cases include automating the creation of subaccounts in Kobana as part of onboarding workflows or managing multiple accounts programmatically. For example, a finance team could use this node to automatically provision subaccounts for different departments or clients without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the data required to create a new subaccount in Kobana. This must be provided and should conform to the API's expected schema for subaccount creation. |
| Additional Fields | Optional JSON object containing extra fields to include in the request. Useful for adding any supplementary parameters supported by the API beyond the main request body. |
Output
- The node outputs the JSON response returned by the Kobana API after creating the subaccount.
- The output is an array of JSON objects, each corresponding to an input item processed.
- The structure of the JSON depends on the API response but typically includes details about the newly created subaccount such as its ID, name, status, and other metadata.
- No binary data output is produced by this node.
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 needed beyond network access to the Kobana API.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" property is malformed, the node will throw a parsing error. Ensure the JSON syntax is correct.
- API Authentication Errors: If the API key credential is missing, invalid, or lacks permissions, the node will fail with authentication errors. Verify that the API key is correctly configured and has rights to create subaccounts.
- Missing Required Fields: The API may reject requests missing mandatory fields in the request body. Consult the Kobana API documentation to ensure all required properties are included.
- Network Issues: Connectivity problems to the Kobana API endpoint can cause timeouts or failures. Check network settings and firewall rules.
- Error Responses from API: The node returns error messages from the API in the output if the request fails. Review these messages to identify issues like validation errors or quota limits.
Links and References
- Kobana API Documentation (general reference for API endpoints and request schemas)
- n8n Documentation on Creating Custom Nodes
