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 SMS delivery records under the "V1 > SMS Deliveries" resource. Specifically, the "Get Many" operation allows users to retrieve multiple SMS delivery entries from their Kobana account. This is useful for scenarios where you want to list or analyze bulk SMS delivery data, such as monitoring message statuses, auditing communications, or integrating SMS delivery logs into other workflows.

For example, a user might want to fetch all SMS deliveries within a certain date range or filter by status to identify failed messages and trigger alerts or retries.

Properties

Name Meaning
Return All Whether to return all SMS delivery results or limit the number of results returned.
Limit The maximum number of SMS delivery results to return (applicable only if Return All is false). Allowed values: 1 to 100.
Additional Fields JSON object containing additional fields to include in the request for filtering or customization.
Query Parameters JSON object with query parameters to filter or modify the retrieval of SMS deliveries (e.g., date ranges, status filters).

Output

The node outputs an array of JSON objects representing SMS delivery records retrieved from the Kobana API. Each object contains details about an individual SMS delivery, such as recipient information, message content, delivery status, timestamps, and any metadata provided by the API.

The output does not include binary data; it is purely JSON structured data suitable for further processing, filtering, or storage within n8n workflows.

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:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid JSON in the "Additional Fields" or "Query Parameters" properties may result in request errors.
    • Exceeding the allowed limit (more than 100) when "Return All" is false will be rejected by the API.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • JSON parsing errors suggest malformed JSON input in the properties; ensure valid JSON syntax.
    • Rate limiting or quota exceeded errors require checking Kobana API usage limits.
    • If the node throws unknown errors, enabling "Continue On Fail" can help isolate problematic items without stopping the entire workflow.

Links and References

Discussion