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
The node provides integration with the Kobana API, enabling users to perform various administrative and transactional operations programmatically. Specifically, for the Admin > Subaccounts resource with the Update operation, this node allows updating details of a subaccount by specifying its ID and providing the updated data in JSON format.
This is useful in scenarios where you need to automate management of subaccounts within an organization, such as changing configuration settings, updating metadata, or modifying permissions without manual intervention.
Practical example:
You have multiple subaccounts representing different departments or clients. When a department changes its billing information or contact details, you can use this node to update the subaccount automatically based on incoming data from other systems.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the subaccount to update. |
| Request Body | A JSON object containing the fields and values to update in the subaccount. |
| Additional Fields | Optional JSON object with extra fields to include in the request (not mandatory). |
Output
- The output is a JSON object representing the updated subaccount resource as returned by the Kobana API.
- The structure depends on the API response but typically includes the subaccount's current state after the update.
- No binary data output is involved.
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:
- Invalid or missing subaccount ID will cause the API to return an error.
- Malformed JSON in the "Request Body" property will result in parsing errors before the request is sent.
- Insufficient permissions or invalid API credentials may lead to authentication failures.
- Network connectivity issues can prevent reaching the Kobana API endpoint.
Error messages and resolutions:
"Invalid ID"or"Resource not found": Verify that the provided subaccount ID exists and is correct."Malformed JSON": Ensure the JSON in the Request Body is valid and properly formatted."Authentication failed": Check that the API key credential is correctly configured and has necessary permissions."API rate limit exceeded": Implement retry logic or reduce request frequency.
Links and References
- Kobana API Documentation (generic placeholder, replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- JSON Validator tools for verifying request body formatting
If you want me to extract details for other resources or operations, just let me know!
