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 interacts with the Kobana API to manage transfer batches, specifically allowing users to create new transfer batches. It is useful in scenarios where you need to automate or integrate batch transfers of funds within financial workflows, such as payroll processing, vendor payments, or bulk internal transfers.
For example, a finance team could use this node to programmatically create batches of transfers to multiple recipients at once, streamlining payment operations and reducing manual effort.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the details of the transfer batch to be created. This includes all necessary fields required by the Kobana API for batch creation. |
| Additional Fields | A JSON object with any additional optional fields that can be included in the request to customize the batch creation further. |
Output
The node outputs the JSON response returned by the Kobana API after creating the transfer batch. This typically includes details about the newly created batch such as its ID, status, creation timestamp, and other metadata provided by the API.
The output is structured as an array of JSON objects, each corresponding to an input item processed. There is no binary data output from this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- Network connectivity to the Kobana API endpoints is necessary.
Troubleshooting
- Invalid JSON in Request Body: If the "Request Body" property contains malformed JSON, the node will fail. Ensure the JSON syntax is correct.
- Missing Required Fields: The API may reject requests missing mandatory fields in the body. Verify the required fields according to Kobana's API documentation.
- Authentication Errors: If the API key or credentials are invalid or expired, authentication errors will occur. Check and update the API credentials in n8n.
- API Rate Limits or Quotas: Excessive requests might lead to rate limiting. Implement error handling or delays if needed.
- Network Issues: Connectivity problems to the Kobana API endpoint will cause failures. Confirm network access and proxy settings if applicable.
Links and References
- Kobana API Documentation (official API docs for detailed request/response schemas)
- n8n Documentation on Using Credentials
