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 webhook deliveries, specifically supporting an "Update" operation for webhook delivery resources under version 1 (V1). The update operation allows users to modify existing webhook delivery records by specifying their ID and providing a JSON request body with the desired changes.
Common scenarios where this node is beneficial include:
- Updating the status or details of a webhook delivery after it has been processed.
- Correcting or adding information to a webhook delivery record.
- Automating updates to webhook deliveries as part of a larger workflow involving event handling or notification systems.
For example, you might use this node to update the payload or metadata of a webhook delivery after receiving new information from an external system or to mark a delivery as retried or acknowledged.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the webhook delivery resource to update. |
| Request Body | A JSON object representing the fields and values to update in the webhook delivery. |
| Additional Fields | Optional JSON object with extra fields for the request (not typically used in update). |
Output
The node outputs a JSON array where each item corresponds to the updated webhook delivery resource returned by the Kobana API. The structure of the JSON output reflects the updated state of the webhook delivery, including all its properties as returned by the API.
If the API supports binary data for webhook deliveries (not indicated here), the node would handle it accordingly, but based on the code and properties, the output is purely JSON.
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 other external dependencies are required beyond the Kobana API access.
Troubleshooting
- Invalid ID: If the provided ID does not correspond to an existing webhook delivery, the API will likely return an error indicating the resource was not found. Verify the ID before running the node.
- Malformed JSON in Request Body: The "Request Body" must be valid JSON. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting.
- Authentication Errors: Ensure that the API key credential is correctly configured and has sufficient permissions to update webhook deliveries.
- API Environment Mismatch: The node uses different base URLs for production and sandbox environments. Make sure the credential environment matches your intended target.
- Unhandled API Errors: If the API returns unexpected errors, enable "Continue On Fail" in the node settings to capture error messages in the output for debugging.
Links and References
- Kobana API Documentation (general reference; specific endpoint docs may be available there)
- n8n documentation on Creating Custom Nodes
- JSON validation tools such as JSONLint for verifying request body syntax
