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 records under the "V1 > Webhook Deliveries" resource. Specifically, the "Get Many" operation allows users to retrieve multiple webhook delivery entries from their Kobana account. This is useful for monitoring and auditing webhook events, troubleshooting webhook issues, or analyzing webhook delivery performance.
Practical examples include:
- Fetching all webhook deliveries within a certain time frame to verify successful event notifications.
- Retrieving a limited number of recent webhook deliveries for quick inspection.
- Applying query parameters to filter webhook deliveries by status, date, or other criteria supported by the API.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return (applicable if "Return All" is false). |
| Additional Fields | JSON object with additional fields for the request (optional extra parameters). |
| Query Parameters | JSON object with query parameters to filter or modify the request (e.g., filtering options). |
Output
The node outputs an array of JSON objects representing webhook delivery records retrieved from the Kobana API. Each object corresponds to a single webhook delivery entry containing details such as delivery status, timestamps, payload data, and any metadata provided by the API.
If the API supports binary data for webhook deliveries (not indicated in this code), it would be summarized accordingly; however, this node primarily returns JSON data.
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 standard HTTP requests to the Kobana API.
Troubleshooting
Common Issues:
- Authentication failures due to missing or invalid API credentials.
- Exceeding rate limits imposed by the Kobana API.
- Incorrectly formatted JSON in "Additional Fields" or "Query Parameters" causing request errors.
- Requesting more items than allowed by the API limit.
Error Messages:
- Errors returned from the API will be included in the output if "Continue On Fail" is enabled.
- Typical error messages may include authentication errors, invalid parameter errors, or network issues.
Resolutions:
- Verify that the API key credential is correctly configured and has necessary permissions.
- Ensure JSON inputs for additional fields and query parameters are valid.
- Use the "Limit" property to restrict the number of results if not returning all.
- Check network connectivity and API status.
Links and References
- Kobana API Documentation (general reference for API endpoints and parameters)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n workflows
