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 update an existing event resource in the V1 Events category. It allows users to modify details of a specific event by providing its unique ID and the updated data in JSON format. This operation is useful for scenarios where event information needs correction or enhancement after creation, such as updating event metadata, status, or other attributes.
Practical examples include:
- Changing the date or description of an event.
- Updating event status or related custom fields.
- Modifying any other event properties supported by the Kobana API.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the event resource to update. |
| Request Body | The JSON object containing the fields and values to update on the event resource. |
| Additional Fields | Optional JSON object with extra fields to include in the request (not mandatory here). |
Output
The node outputs the JSON response returned by the Kobana API after the update operation. This typically includes the updated event object with all its properties reflecting the changes made.
- The output is structured as an array of JSON objects, each representing the updated event.
- No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n for authentication.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- The request uses HTTP PUT method to update the event resource at the endpoint
/v1/events/{id}.
Troubleshooting
- Invalid ID: If the provided event ID does not exist, the API will likely return a "resource not found" error. Verify the ID correctness.
- Malformed JSON: The "Request Body" must be valid JSON. Invalid JSON will cause parsing errors before the request is sent.
- Authentication errors: Ensure the Kobana API credential is correctly set up and has permissions to update events.
- API limits or network issues: Temporary failures may occur due to rate limiting or connectivity; retrying might help.
- If "continue on fail" is enabled, errors will be returned as part of the output JSON with an
errorfield.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes
