Kobana icon

Kobana

Interact with Kobana API - Quick access to common operations
Join our community

Actions215

Overview

This node interacts with the Kobana API to manage webhooks and other resources. Specifically, for the V1 > Webhooks resource with the Get Many operation, it retrieves multiple webhook records from the Kobana system. This is useful when you want to list all existing webhooks or filter them based on query parameters.

Common scenarios include:

  • Fetching all configured webhooks to audit or monitor integrations.
  • Retrieving a subset of webhooks filtered by specific criteria (e.g., status, creation date).
  • Automating workflows that depend on webhook configurations stored in Kobana.

Example use case:

  • An automation that periodically fetches all webhooks to verify their status or update a dashboard.

Properties

Name Meaning
Return All Whether to return all webhook results or limit the number of returned items.
Limit Maximum number of webhook results to return if "Return All" is false (1 to 100).
Additional Fields JSON object with additional fields to include in the request (optional extra parameters).
Query Parameters JSON object with query parameters to filter or modify the list request (e.g., filters).

Output

The node outputs an array of JSON objects representing the webhooks retrieved from the Kobana API. Each object corresponds to a webhook and contains its properties as returned by the API, such as ID, URL, events subscribed to, status, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Kobana API.
  • The node automatically 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:

    • Authentication errors due to missing or invalid API credentials.
    • Request limits exceeded if too many items are requested without pagination.
    • Malformed JSON in "Additional Fields" or "Query Parameters" causing request failures.

  • Error messages:

    • "Unauthorized" or similar indicates invalid or missing API authentication token; verify credentials.
    • "Bad Request" may indicate invalid query parameters or JSON syntax errors; check JSON formatting.
    • "Too Many Requests" suggests hitting API rate limits; reduce request frequency or batch size.

  • Resolutions:

    • Ensure valid API credentials are configured in n8n.
    • Validate JSON inputs using a JSON validator before running the node.
    • Use "Return All" carefully and consider setting reasonable limits to avoid large payloads.

Links and References

Discussion