Kobana icon

Kobana

Interact with Kobana API - Quick access to common operations

Actions215

Overview

This node integrates with the Kobana API to manage transfer batches, specifically allowing users to update existing transfer batch resources. It is useful in scenarios where you need to modify details of a transfer batch such as changing metadata or updating batch parameters after creation.

For example, if you have created a transfer batch and later need to adjust some fields (like adding notes or changing status flags), this node's update operation lets you send those changes directly to the Kobana system via its API.

Properties

Name Meaning
ID The unique identifier of the transfer batch resource to update.
Request Body A JSON object representing the fields and values to update on the transfer batch resource.
  • ID: Required string input specifying which transfer batch to update.
  • Request Body: Required JSON input containing the data to update on the batch. This should be a valid JSON object matching the API's expected schema for transfer batch updates.

Output

The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated transfer batch object with all its current properties reflecting the changes made.

The output is structured as an array of JSON objects, each representing the updated resource corresponding to an input item.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Kobana API credential configured in n8n, providing necessary authentication tokens.
  • The node dynamically selects the API base URL depending on the environment (production or sandbox).
  • The request uses standard HTTP methods and expects JSON payloads.

Troubleshooting

  • Invalid ID: If the provided ID does not correspond to an existing transfer batch, the API will likely return a 404 error. Verify the ID is correct.
  • Malformed JSON in Request Body: Ensure the JSON entered in the "Request Body" field is valid and matches the expected schema; otherwise, the API may reject the request with a 400 error.
  • Authentication Errors: If credentials are missing or invalid, the node will fail to authenticate. Confirm that the Kobana API credential is properly set up.
  • API Rate Limits or Downtime: Temporary failures might occur due to API limits or service issues. Retrying later or checking the Kobana status page can help.

Links and References

Discussion