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 customer subscriptions and other related resources. Specifically, for the V1 > Customer Subscriptions resource with the Get Many operation, it retrieves multiple customer subscription records from the Kobana system.

Typical use cases include:

  • Fetching a list of all or a limited number of customer subscriptions for reporting or synchronization purposes.
  • Applying query parameters to filter or sort the retrieved subscriptions.
  • Integrating subscription data into workflows that automate billing, notifications, or customer management.

For example, you might use this node to get all active subscriptions to send renewal reminders or to analyze subscription trends over time.

Properties

Name Meaning
Return All Whether to return all subscription results or limit the number returned.
Limit Maximum number of subscription results to return (only used if Return All is false). Range: 1-100
Additional Fields JSON object with additional fields to include in the request (optional).
Query Parameters JSON object with query parameters to filter or modify the request (e.g., filtering by status).

Output

The node outputs an array of JSON objects representing customer subscriptions. Each object corresponds to a subscription record as returned by the Kobana API.

The output structure includes all standard subscription fields provided by the API, such as subscription ID, customer details, status, start/end dates, and any other metadata included in the response.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Kobana API via an API key credential configured in n8n.
  • 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 API credentials will cause authentication failures.
    • Exceeding rate limits imposed by the Kobana API may result in errors or throttled responses.
    • Malformed JSON in "Additional Fields" or "Query Parameters" can cause request parsing errors.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • JSON parse errors suggest incorrect formatting in input JSON fields; ensure valid JSON syntax.
    • HTTP errors from the API (e.g., 400 Bad Request) often relate to invalid query parameters or unsupported filters; review the API documentation for allowed parameters.

Links and References

  • Kobana API Documentation (official API docs for detailed endpoint info)
  • n8n Documentation on HTTP Request Node (for understanding how API requests are made)
  • JSON Validator tools (to validate JSON input for Additional Fields and Query Parameters)

Discussion