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 webhooks under the V1 API version. Specifically, the Create operation for the Webhooks resource allows users to create new webhook configurations in their Kobana account. This is useful for automating event-driven workflows where external systems need to be notified about specific events occurring within Kobana.
Typical use cases include:
- Automatically registering a webhook URL to receive notifications about payment status changes.
- Setting up webhooks to trigger downstream processes when customer subscriptions are updated.
- Creating webhooks dynamically as part of an automated deployment or integration pipeline.
For example, you might use this node to create a webhook that listens for new bank billet payments and triggers further processing in your system.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the webhook configuration details to be created. This must be provided and should conform to the expected schema by the Kobana API for webhook creation. |
| Additional Fields | (Not applicable for this operation) |
The Request Body property is required and expects a JSON object describing the webhook's parameters such as URL, events to subscribe to, and other settings.
Output
The node outputs the JSON response returned by the Kobana API after creating the webhook. This typically includes details of the newly created webhook such as its unique ID, URL, subscribed events, creation timestamp, and status.
The output is structured as an array of JSON objects, each corresponding to an input item processed. Each object contains the full webhook data as returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions to create webhooks.
- The node communicates with either the production or sandbox Kobana API endpoints depending on the environment specified in the credentials.
- No additional external dependencies beyond the Kobana API and n8n's HTTP request capabilities.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" field is malformed, the node will throw a parsing error. Ensure the JSON syntax is correct before execution.
- Authentication Errors: If the API key or credentials are invalid or missing, the node will fail with authentication errors. Verify that the Kobana API credential is correctly set up and has necessary permissions.
- API Endpoint Issues: Network issues or incorrect environment selection (production vs sandbox) can cause connection failures. Confirm network connectivity and credential environment settings.
- Missing Required Fields: The Kobana API may reject requests missing mandatory webhook fields. Double-check the required properties in the JSON body according to Kobana's API documentation.
Links and References
- Kobana API Documentation — Official API docs for webhook creation and other operations.
- n8n Documentation — General guidance on using HTTP request nodes and managing credentials in n8n.
