Kobana icon

Kobana

Interact with Kobana API - Quick access to common operations

Actions215

Overview

This node integrates with the Kobana API to manage bank billets (bank slips) and other related financial resources. Specifically, the V1 > Bank Billets - Get operation retrieves detailed information about a single bank billet by its unique ID.

This operation is useful in scenarios where you need to fetch the current status, payment details, or metadata of a specific bank slip. For example, you might use it to verify if a bank billet has been paid, to display payment information to a customer, or to audit billing records.

Properties

Name Meaning
ID The unique identifier of the bank billet to retrieve. This is a required string input.

Output

The node outputs a JSON object representing the bank billet resource retrieved from the Kobana API. The structure typically includes fields such as the billet's ID, amount, due date, status, payer information, and payment details.

The output is provided as an array of JSON objects (one per input item), each containing the full data of the requested bank billet.

No binary data is output by 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).
  • The node uses HTTP GET requests to fetch data from the endpoint /v1/bank_billets/{id}.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent bank billet ID will likely result in an error response from the API.
    • Network connectivity issues or incorrect API credentials will cause authentication or request failures.
    • JSON parsing errors may occur if the input parameters are malformed.
  • Error messages:

    • Errors returned by the Kobana API will be passed through in the output as an error object.
    • If the node is set to continue on failure, errors for individual items will be included in the output JSON with an error field describing the issue.
  • Resolution tips:

    • Verify the correctness of the bank billet ID.
    • Ensure the API key credential is valid and has the necessary permissions.
    • Check network connectivity and API endpoint availability.
    • Use the node's "continue on fail" option to handle errors gracefully in workflows.

Links and References

Discussion