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 internal transfer batches within a financial or payment system. Specifically, the Transfer > Internal Batches > Create operation allows users to create new internal transfer batches by sending a JSON-formatted request body describing the batch details.
Typical use cases include automating the creation of grouped internal transfers for accounting, payroll, or inter-departmental fund movements within an organization. For example, a finance team could use this node to programmatically create batches of internal transfers to multiple accounts in one API call, streamlining bulk transfer processes.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the details of the internal transfer batch to be created. This must include all required fields as per the Kobana API specification for creating internal transfer batches. |
| Additional Fields | Optional JSON object containing any extra fields to include in the request. This allows 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 internal transfer batch. This typically includes details such as the batch ID, status, creation timestamp, and any other metadata provided by the API about the newly created batch.
If the API supports binary data output (not indicated here), it would be summarized accordingly, but in this case, the output is purely JSON.
Dependencies
- Requires an active Kobana API credential configured in n8n, which provides authentication tokens or API keys necessary to authorize requests.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- The user must provide valid JSON input for the request body according to the Kobana API schema for internal transfer batches.
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 that the JSON syntax is correct before running the node.
- Authentication Errors: If the Kobana API credentials are missing, invalid, or expired, the node will fail to authenticate. Verify that the API key or token is correctly set up in n8n credentials.
- API Validation Errors: The Kobana API may reject the request if required fields are missing or contain invalid values. Review the API documentation to ensure the request body meets all requirements.
- Network Issues: Connectivity problems or incorrect environment selection (sandbox vs production) can cause request failures. Confirm network access and environment settings.
Links and References
- Kobana API Documentation (general reference for API endpoints and request schemas)
- n8n Documentation on Creating Custom Nodes
- JSON validation tools (e.g., https://jsonlint.com/) to verify request body correctness before execution
