Kobana icon

Kobana

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

Actions215

Overview

This node allows you to interact with the Kobana API specifically for managing internal transfers under the "Transfer > Internal" resource. The "Update" operation lets you update an existing internal transfer by specifying its ID and providing a JSON request body with the fields to modify.

Typical use cases include automating updates to internal transfer records such as changing amounts, dates, or statuses within your financial workflows. For example, you might update an internal transfer's details after receiving new information or correcting errors without manually accessing the Kobana dashboard.

Properties

Name Meaning
ID The unique identifier of the internal transfer to update.
Request Body A JSON object containing the fields and values to update on the internal transfer record.

Note: There is also an "Additional Fields" collection available in other operations but it is not applicable for this specific "update" operation on "Transfer > Internal".

Output

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

If the API returns an error, the output will contain an error message describing what went wrong.

No binary data output is involved in this operation.

Dependencies

  • Requires an active Kobana API credential configured in n8n with appropriate permissions.
  • The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
  • The node uses HTTP methods (PUT for update) to communicate with the Kobana REST API.

Troubleshooting

  • Invalid ID: If the provided ID does not correspond to an existing internal transfer, the API will return an error. Verify the ID before running the node.
  • Malformed JSON: The "Request Body" must be valid JSON. Invalid JSON syntax will cause parsing errors.
  • Permission Errors: Ensure the API key has rights to update internal transfers.
  • API Endpoint Issues: Network issues or incorrect environment settings can cause connection failures.
  • Error Messages: The node surfaces API error messages in the output JSON under an error field. Review these messages to identify issues like missing required fields or invalid values.

Links and References

Discussion