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 financial account balances and related operations. Specifically, for the Financial > Balances resource with the Create operation, it allows users to create new balance records or entries in their financial accounts.
Typical use cases include:
- Automating the creation of new balance entries when transactions occur.
- Integrating with accounting or ERP systems to keep financial balances up-to-date.
- Creating initial balances or adjustments programmatically as part of a financial workflow.
For example, a user might send a JSON payload describing a new balance record (such as an opening balance or adjustment) to the Kobana API via this node, which then creates the balance entry in the system.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the details of the balance to create. This is required and should contain all necessary fields as per the Kobana API specification for creating balances. |
| Additional Fields | Optional JSON object with extra fields that can be included in the request to customize or extend the creation parameters. |
The "Request Body" property must be provided by the user and contains the core data for the balance creation. The "Additional Fields" property allows adding any other optional parameters supported by the API in JSON format.
Output
The node outputs the JSON response returned by the Kobana API after creating the balance. This typically includes the newly created balance's details such as its ID, amount, associated account, timestamps, and status.
The output is structured as an array of JSON objects, each corresponding to an input item processed. Each object contains the full response from the API for that particular creation request.
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).
- The user must configure the Kobana API credentials in n8n before using this node.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" or "Additional Fields" is malformed, the node will throw a parsing error. Ensure valid JSON syntax.
- Authentication Errors: If the API key credential is missing or invalid, requests will fail with authentication errors. Verify the configured credentials.
- API Validation Errors: The Kobana API may reject requests if required fields are missing or contain invalid values. Review the API documentation and ensure the JSON body meets all requirements.
- Network Issues: Connectivity problems to the Kobana API endpoints can cause timeouts or failures. Check network access and endpoint availability.
If the node is set to continue on failure, errors for individual items will be returned in the output JSON under an error field.
Links and References
- Kobana API Documentation (official API docs for detailed request/response schemas)
- n8n Documentation on Creating Custom Nodes
- JSON Validator tools (e.g., https://jsonlint.com/) for verifying JSON syntax before use
