Kobana icon

Kobana

Interact with Kobana API - Quick access to common operations

Actions215

Overview

This node interacts with the Kobana API to manage internal transfer batches within the "Transfer > Internal Batches" resource. Specifically, the Get operation retrieves detailed information about a single internal transfer batch by its unique ID.

Typical use cases include:

  • Fetching the status and details of a specific internal transfer batch for reconciliation or auditing.
  • Integrating Kobana's internal transfer batch data into workflows for reporting or further processing.
  • Automating monitoring and alerting based on batch information retrieved from Kobana.

Example: You have an internal transfer batch ID and want to retrieve all associated data such as transfers included, status, timestamps, and metadata to verify processing or trigger downstream actions.

Properties

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

Output

The node outputs JSON data representing the internal transfer batch details as returned by the Kobana API. The structure typically includes fields such as batch ID, creation date, status, list of transfers in the batch, and other metadata related to the internal transfer batch.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Kobana API credential configured in n8n to authenticate requests.
  • The node dynamically selects the API base URL depending on the environment (production or sandbox).
  • Network access to the Kobana API endpoints is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing batch ID will cause the API to return an error.
    • Authentication failures if the Kobana API credential is not set up correctly.
    • Network connectivity problems to the Kobana API endpoint.
  • Error messages:

    • Errors from the Kobana API are returned in the output JSON under an error field when "Continue On Fail" is enabled.
    • Typical errors include "Resource not found" if the ID does not exist, or "Unauthorized" if credentials are invalid.
  • Resolutions:

    • Verify the batch ID is correct and exists in Kobana.
    • Ensure the Kobana API credential is properly configured and has necessary permissions.
    • Check network connectivity and firewall settings allowing access to the Kobana API.

Links and References

Discussion