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 provides integration with the Kobana API, enabling users to perform various operations on multiple resources related to financial and customer management. Specifically, for the V1 > Webhooks resource with the Get operation, the node retrieves detailed information about a specific webhook by its ID.
Common scenarios where this node is beneficial include:
- Automating retrieval of webhook configurations or statuses in Kobana.
- Integrating webhook data into workflows for monitoring or auditing purposes.
- Fetching webhook details dynamically based on user input or other workflow data.
Practical example:
- A user wants to fetch the configuration details of a particular webhook to verify its URL or event subscriptions before updating it or troubleshooting delivery issues.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the webhook resource to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the webhook object retrieved from the Kobana API. The structure corresponds to the webhook's properties as defined by the Kobana service, typically including fields such as webhook ID, URL, subscribed events, status, creation date, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n, which includes necessary authentication tokens or API keys.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Network access to the Kobana API endpoints is required.
Troubleshooting
Common Issues:
- Invalid or missing webhook ID: The node requires a valid webhook ID; providing an empty or incorrect ID will result in an error.
- Authentication failures: Ensure that the Kobana API credentials are correctly set up and have sufficient permissions.
- Network connectivity problems: Verify that the n8n instance can reach the Kobana API endpoints.
Error Messages:
"404 Not Found": The specified webhook ID does not exist. Confirm the ID is correct."401 Unauthorized"or"403 Forbidden": Authentication failed or insufficient permissions. Check API credentials."Invalid JSON": If custom JSON inputs are malformed, ensure proper JSON formatting.
Resolving these errors typically involves verifying input parameters, checking credentials, and ensuring network connectivity.
Links and References
- Kobana API Documentation (general reference for API endpoints and webhook resource)
- n8n documentation on API Credentials for setting up API authentication
