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 allows you to interact with the Kobana API, specifically managing EDI Boxes when using the "EDI > EDI Boxes" resource. The "Update" operation lets you update an existing EDI Box by specifying its ID and providing a JSON request body with the fields to modify.
Common scenarios for this node include automating updates to EDI Boxes in your Kobana account, such as changing configuration details or metadata without manual intervention. For example, you might update connection parameters or status flags of an EDI Box as part of a workflow that monitors and manages electronic data interchange processes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the EDI Box resource you want to update. |
| Additional Fields | A JSON object containing any extra fields to include in the request (optional). |
| Request Body | The JSON-formatted request body specifying the fields and values to update on the EDI Box. |
- ID is required and identifies which EDI Box will be updated.
- Additional Fields is optional and can contain any supplementary parameters as a JSON object.
- Request Body is required and must be a valid JSON object describing the updates to apply.
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated EDI Box data reflecting the changes made.
- The output is structured as an array of JSON objects, each representing the updated resource.
- No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions to update EDI Boxes.
- 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 ID error: If the provided ID does not correspond to an existing EDI Box, the API will return an error. Verify the ID is correct.
- Malformed JSON in Request Body: Ensure the JSON in the "Request Body" property is well-formed; otherwise, the request will fail.
- Authentication errors: Confirm that the Kobana API credentials are valid and have sufficient permissions.
- API rate limits or downtime: Temporary failures may occur if the API is unavailable or rate limits are exceeded. Retry later or check API status.
- Unexpected errors: If the node throws unknown errors, enable "Continue On Fail" to handle errors gracefully within workflows.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- n8n documentation on Using Credentials
- JSON formatting guides for constructing valid request bodies
