Kobana icon

Kobana

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

Actions215

Overview

This node provides integration with the Kobana API, enabling users to perform various operations on multiple Kobana resources such as bank billets (bank slips), customer subscriptions, webhooks, customers, and more. The "Get" operation for the "Default" resource (which maps to "v1_bank_billets" in this context) allows retrieving a specific bank slip by its ID.

Typical use cases include:

  • Fetching detailed information about a specific bank slip by its unique identifier.
  • Automating workflows that require verification or processing of bank slip data.
  • Integrating Kobana's financial document management into broader automation pipelines.

For example, a user can input a bank slip ID to retrieve its status and details, then use that data to trigger further actions such as payment confirmation or notification sending.

Properties

Name Meaning
ID The unique identifier of the bank slip (bank billet) to retrieve. This is a required string input for the "Get" operation on the Default resource.

Output

The node outputs JSON data representing the retrieved bank slip's details from the Kobana API. The structure typically includes all relevant fields of the bank slip such as amount, due date, status, payer information, and other metadata provided by Kobana.

No binary data output is involved in 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 needed beyond the Kobana API access.

Troubleshooting

  • Common issues:

    • Invalid or missing bank slip ID: The node requires a valid ID; providing an empty or incorrect ID will cause errors.
    • Authentication failures: Ensure the API key credential is correctly configured and has necessary permissions.
    • Network or API endpoint issues: Verify connectivity and correct environment selection (sandbox vs production).

  • Common error messages:

    • "Resource not found" or similar errors indicate the specified bank slip ID does not exist.
    • Authentication errors suggest invalid or expired credentials.
    • JSON parsing errors may occur if the input body or parameters are malformed (not applicable for simple "Get" but relevant for other operations).

To resolve these:

  • Double-check the ID value.
  • Confirm API credentials and environment settings.
  • Review API documentation for correct usage and parameter formats.

Links and References

Discussion