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 Update operation for the Transfer > Internal Batches resource allows users to modify existing internal transfer batch records by sending updated data in JSON format.
Typical use cases include:
- Adjusting details of an internal transfer batch after its creation (e.g., changing amounts, dates, or metadata).
- Automating updates to batches based on external triggers or workflows.
- Synchronizing batch information between Kobana and other systems.
For example, you might update the status or add additional fields to an internal transfer batch to reflect changes in processing or reconciliation.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the internal transfer batch to update. |
| Request Body | A JSON object containing the fields and values to update in the internal transfer batch. |
Details:
- ID: Required string that specifies which internal batch record to update.
- Request Body: Required JSON input where you specify the new values for the batch's properties. This must be a valid JSON object matching the API's expected schema for internal batch updates.
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated internal batch object with all its current properties as stored in Kobana.
- The output is structured as an array of JSON objects, each representing the updated batch data.
- No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n, providing authentication to access the Kobana environment.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- The request uses standard HTTP methods (PUT) and expects JSON payloads.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" property is malformed, the node will fail. Ensure the JSON syntax is correct.
- Missing or Incorrect ID: The update operation requires a valid batch ID. Providing an incorrect or missing ID will result in an error from the API.
- API Authentication Errors: If the API credentials are invalid or expired, requests will fail. Verify the API key/token and permissions.
- API Endpoint Errors: If the batch ID does not exist or the user lacks permission to update it, the API will return an error. Check the batch ID and user rights.
- Network Issues: Connectivity problems can cause request failures. Confirm network access to the Kobana API endpoints.
Links and References
- Kobana API Documentation (general reference for API endpoints and schemas)
- n8n documentation on HTTP Request Node for understanding how API calls are made
- JSON validation tools such as JSONLint to verify request body correctness
