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 TED transfer batches, specifically supporting the Update operation on TED Batches within the Transfer resource. It allows users to update details of an existing TED batch by specifying its ID and providing a JSON request body with the fields to modify.
Typical use cases include:
- Modifying batch metadata or properties after creation.
- Adjusting batch parameters before processing transfers.
- Automating updates to TED batches as part of larger financial workflows.
For example, you might update the description or status of a TED batch programmatically based on external triggers or business logic.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the TED batch to update. |
| Request Body | A JSON object containing the fields and values to update in the TED batch. This is required. |
Note: There is also an "Additional Fields" collection available generally for other operations, but for the Update operation on TED Batches, the main inputs are the ID and the JSON request body.
Output
The node outputs the JSON response returned by the Kobana API after updating the TED batch. This typically includes the updated batch data structure reflecting the changes made.
The output is structured as an array of JSON objects, each representing the updated resource data for each input item processed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- No additional external dependencies are needed beyond the Kobana API access.
Troubleshooting
- Invalid ID error: If the provided batch ID does not exist or is malformed, the API will return an error. Verify the ID correctness.
- Malformed JSON in Request Body: Ensure the JSON provided in the "Request Body" field is valid and matches the expected schema for TED batch updates.
- Authentication errors: Confirm that the API key credential is correctly configured and has permissions to update TED batches.
- API environment mismatch: Using sandbox credentials against the production endpoint or vice versa may cause failures; ensure environment selection matches credentials.
- 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 (general reference for API endpoints and data models)
- n8n documentation on Creating Custom Nodes
