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 perform various operations on different resources. Specifically, for the V1 > Reports resource with the Get operation, it retrieves a report by its unique ID. This is useful when you need to fetch detailed information or data about a specific report stored in Kobana.

Common scenarios include:

  • Fetching a financial or operational report by its ID for review or processing.
  • Integrating Kobana reports into automated workflows for reporting or analytics.
  • Retrieving report data to trigger further actions based on report contents.

Example: You have generated a report in Kobana and want to pull its details into your workflow to analyze or send via email automatically.

Properties

Name Meaning
ID The unique identifier of the report to retrieve. This is required to specify which report to get.

Output

The node outputs the JSON data returned by the Kobana API for the requested report. This typically includes all fields and metadata associated with that report as defined by Kobana's API.

  • The output is an array of JSON objects, each representing the report data.
  • 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

  • Missing or invalid ID: The "ID" property is required. If omitted or incorrect, the API will likely return an error indicating the resource was not found.
  • Authentication errors: Ensure the API key credential is correctly configured and has permissions to access reports.
  • Network or API endpoint issues: Verify network connectivity and that the correct environment (production vs sandbox) is selected.
  • JSON parsing errors: Input properties like "body" or query parameters must be valid JSON if used in other operations; for "get" operation on reports, this is not applicable but relevant for others.

If the node throws an error, check the error message for clues such as "Not Found", "Unauthorized", or "Bad Request" and verify the corresponding input or credentials.

Links and References

Discussion