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 TED (Electronic Transfer Document) transfers, specifically supporting the Update operation for TED transfers. It allows users to update existing TED transfer records by specifying the transfer ID and providing a JSON request body with the updated data.
Typical use cases include:
- Modifying details of a scheduled or pending TED transfer.
- Correcting information on an existing TED transfer without creating a new one.
- Automating updates to TED transfers as part of financial workflows.
For example, a user might update the beneficiary's bank account details or change the transfer amount before execution.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the TED transfer to update. |
| Request Body | A JSON object containing the fields and values to update in the TED transfer record. |
| Additional Fields | Optional JSON object with extra fields for the request (not mandatory for update operation). |
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated TED transfer object with its current state and all relevant properties reflecting the changes made.
If the API returns binary data (not typical for update operations), it would represent file contents or attachments related to the transfer, but this is not applicable here.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Network access to
https://api.kobana.com.br(production) orhttps://api-sandbox.kobana.com.br(sandbox) is required.
Troubleshooting
- Invalid ID error: Ensure the provided TED transfer ID exists and is correctly formatted.
- Malformed JSON in Request Body: The "Request Body" must be valid JSON; invalid syntax will cause errors.
- Authentication failures: Verify that the Kobana API credentials are correct and have sufficient permissions.
- API rate limits or downtime: Temporary network or API issues may cause failures; retry or check Kobana status.
- Unexpected errors: Enable "Continue On Fail" in the node settings to handle errors gracefully and inspect error messages in output.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using Credentials
- n8n documentation on JSON Parameters
