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 accounts and related resources. Specifically, for the Financial > Accounts resource with the Create operation, it allows users to create new financial account records by sending a JSON-formatted request body to the Kobana API.
Typical use cases include automating the creation of billing wallets or financial accounts within a financial system, enabling seamless integration between n8n workflows and Kobana's financial services platform. For example, when onboarding a new client or setting up a new billing wallet, this node can programmatically create the necessary account in Kobana without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the data required to create the financial account. This must be provided and should conform to the expected schema of the Kobana API for account creation. |
| Additional Fields | Optional JSON object containing extra fields to include in the request. Useful for adding custom or less common parameters supported by the API. |
Output
The node outputs the JSON response returned by the Kobana API after creating the financial account. This typically includes details of the newly created account such as its ID, status, and any other metadata provided by the API.
The output is structured as an array of JSON objects, each corresponding to an input item processed. Each object contains the full API response under the json field.
No binary data output is produced by this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n, which provides authentication tokens or API keys needed to authorize requests.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Network access to the Kobana API endpoints is necessary.
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 credentials are missing, invalid, or expired, the node will fail with an authentication error. Verify that the Kobana API credential is correctly set up and has proper permissions.
- API Validation Errors: The Kobana API may reject the request if required fields are missing or contain invalid values. Review the API documentation for required fields and validate your JSON accordingly.
- Network Issues: Connectivity problems to the Kobana API endpoint will cause request failures. Check network settings and firewall rules.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- Kobana API Documentation (Please refer to the official Kobana API docs for detailed schema and examples)
- n8n Documentation: Working with HTTP Request Nodes (for understanding how API calls are made)
If you need further details about other operations or resources, feel free to ask!