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
The node provides integration with the Kobana API, specifically allowing management of webhooks under the V1 API version. The "Update" operation for the "Webhooks" resource enables users to modify an existing webhook by specifying its ID and providing a JSON request body with the updated data.
This node is useful in scenarios where you need to programmatically update webhook configurations such as URLs, events subscribed to, or other webhook settings within Kobana. For example, you might want to change the target URL of a webhook after deployment changes or update event filters dynamically based on workflow conditions.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the webhook to update. |
| Request Body | A JSON object containing the fields and values to update on the webhook resource. |
| Additional Fields | (Not specifically used in this operation but available) JSON object with extra parameters. |
Output
- The output is a JSON object representing the updated webhook resource as returned by the Kobana API.
- The structure corresponds to the webhook's properties after the update.
- No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node automatically selects the API base URL depending on whether the environment is production or sandbox.
- No additional external dependencies are required beyond the Kobana API access.
Troubleshooting
- Invalid ID: If the provided webhook ID does not exist, the API will likely return a 404 error. Verify the ID is correct.
- Malformed JSON: The "Request Body" must be valid JSON. Invalid JSON will cause parsing errors before the request is sent.
- Authentication Errors: Ensure the API key credential is correctly configured and has permissions to update webhooks.
- API Rate Limits: Frequent updates may hit rate limits; handle errors accordingly.
- Unexpected API Response: If the API changes or returns unexpected data, verify the node version compatibility.
Links and References
- Kobana API Documentation (general reference for API endpoints and webhook management)
- n8n Documentation on Creating Custom Nodes
