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 transfers within the "Transfer > Internal" resource. Specifically, the "Create" operation allows users to initiate new internal transfer requests by sending a JSON-formatted request body to the Kobana API.
Typical use cases include automating internal fund movements between accounts in financial workflows, integrating internal transfer processes into larger automation pipelines, or triggering transfers based on external events.
For example, a user might configure this node to create an internal transfer whenever a certain invoice is paid, moving funds from one internal account to another automatically.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the details of the internal transfer to be created. This must include all required fields as per the Kobana API specification for internal transfers. |
| Additional Fields | A collection allowing the user to add extra JSON fields to the request if needed. This can be used to include optional parameters supported by the API that are not explicitly exposed as separate properties. |
Output
The node outputs the JSON response returned by the Kobana API after creating the internal transfer. This typically includes details about the newly created transfer such as its ID, status, timestamps, and any other metadata provided by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active Kobana API credential configured in n8n, which provides authentication to the Kobana service.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- The request is made over HTTP(S) using standard REST methods.
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.
- Missing Required Fields: The Kobana API may reject requests missing mandatory fields. Verify the request body contains all required properties according to Kobana's API documentation.
- Authentication Errors: If the API credentials are invalid or expired, the node will fail with an authentication error. Check the configured API key or token.
- API Endpoint Errors: Network issues or incorrect API endpoint usage can cause failures. Confirm the environment setting (production vs sandbox) and network connectivity.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON.
Links and References
- Kobana API Documentation (official API docs for detailed request/response schemas)
- n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)
