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 delivery resources, specifically allowing users to retrieve details about a specific webhook delivery by its ID. It is useful in scenarios where you need to track or audit webhook delivery statuses, troubleshoot webhook issues, or integrate webhook delivery data into workflows for monitoring or logging purposes.
For example, if you have set up webhooks to notify your system of certain events, this node can fetch detailed information about each webhook delivery attempt, including success or failure status, timestamps, and payloads.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the webhook delivery resource to retrieve. This property is required. |
Output
The node outputs JSON data representing the webhook delivery resource fetched from the Kobana API. The structure typically includes all relevant details about the webhook delivery such as:
- Delivery ID
- Status (e.g., success, failure)
- Timestamp of delivery attempts
- Payload sent
- Response received from the webhook endpoint
No binary data output is indicated for this operation.
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 additional external dependencies are required beyond the Kobana API access.
Troubleshooting
Common Issues:
- Invalid or missing ID parameter will cause the request to fail.
- Authentication errors if the API key credential is invalid or missing.
- Network connectivity issues may prevent reaching the Kobana API endpoints.
- If the specified webhook delivery ID does not exist, the API will return an error.
Error Messages:
"Resource not found": Check that the provided ID is correct."Unauthorized"or authentication failures: Verify that the API key credential is properly configured."Invalid JSON": Ensure that any JSON inputs (not applicable here since only ID is used) are correctly formatted.
To resolve errors, verify input parameters, ensure valid credentials, and check network connectivity.
Links and References
- Kobana API Documentation (general reference for API endpoints and webhook deliveries)
- n8n documentation on Using API Credentials