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 bank billet batches within the Payment resource. Specifically, the Get operation retrieves detailed information about a specific bank billet batch by its unique ID. This is useful in financial workflows where you need to fetch batch details for reconciliation, reporting, or further processing.

Common scenarios:

  • Retrieving the status and metadata of a particular bank billet batch.
  • Fetching batch details before performing updates or exports.
  • Integrating batch data into accounting or ERP systems.

Practical example:
You have created multiple bank billet batches for different clients and want to retrieve the details of a specific batch to verify its contents or status before sending it for payment processing.

Properties

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

Output

The node outputs a JSON object representing the bank billet batch details as returned by the Kobana API. This typically includes batch metadata such as batch ID, creation date, status, associated bank billets, and other relevant batch information.

If the operation involves exporting (not applicable here), the node might output binary data representing files like ZIP or PDF, but for the Get operation, the output is purely JSON.

Dependencies

  • Requires an active connection to the Kobana API via an API key credential.
  • The node dynamically selects the API base URL depending on the environment (production or sandbox).
  • Proper configuration of the Kobana API credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing batch ID: The node requires a valid batch ID; ensure the ID is correct and exists.
    • Authentication errors: Verify that the Kobana API credentials are correctly set up and have sufficient permissions.
    • Network or API downtime: Check connectivity and Kobana service status if requests fail.

  • Error messages:

    • "Resource not found" or similar indicates the provided batch ID does not exist.
    • "Unauthorized" or "Authentication failed" suggests invalid or expired API credentials.
    • JSON parsing errors may occur if the input body is malformed (not applicable for Get operation).

To resolve these, double-check input parameters, credentials, and network connectivity.

Links and References

Discussion