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 interacts with the Kobana API to manage billing wallets (referred to as "Bank Billet Accounts") in version 1 of the API. Specifically, the Update operation allows users to modify an existing billing wallet by providing its ID and a JSON request body containing the fields to update.
This node is useful in scenarios where you need to programmatically maintain or adjust billing wallet details within Kobana, such as updating account settings, changing wallet attributes, or correcting information without manual intervention.
Practical example:
You have a billing wallet representing a payment collection method for your business. When the wallet's configuration changes (e.g., bank details or wallet parameters), you can use this node to update the wallet automatically based on new data from your system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the billing wallet to update. |
| Request Body | A JSON object representing the fields and values to update in the billing wallet. |
| Additional Fields | Optional JSON object with extra fields for the request (not specifically used in update). |
- ID: Required string input specifying which billing wallet to update.
- Request Body: Required JSON input that contains the update data for the wallet.
- Additional Fields: Optional JSON input for any extra parameters; not mandatory for the update operation.
Output
The output is a JSON array where each item corresponds to the response from the Kobana API after performing the update operation. The structure reflects the updated billing wallet resource as returned by the API.
- The
jsonfield contains the updated billing wallet data. - No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Kobana API via an API key credential configured in n8n.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Proper permissions on the Kobana API are necessary to perform update operations on billing wallets.
Troubleshooting
Common issues:
- Invalid or missing ID: The update will fail if the provided billing wallet ID does not exist or is incorrect.
- Malformed JSON in the Request Body: Ensure the JSON syntax is correct and matches the expected schema for the billing wallet update.
- Insufficient API permissions: The API key must have rights to update billing wallets.
- Network or authentication errors: Verify API credentials and network connectivity.
Error messages:
"Resource not found"or similar indicates the ID may be wrong or the wallet does not exist."Invalid JSON"or parsing errors suggest the request body JSON is malformed.- Authentication errors indicate issues with the API key or credential setup.
To resolve these, double-check the ID, validate JSON formatting, and confirm API credentials and permissions.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- n8n documentation on Using HTTP Request nodes with API keys (for setting up credentials)
