Kobana icon

Kobana

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

Actions215

Overview

This node provides integration with the Kobana API, specifically allowing management of administrative connections when using the Admin > Connections resource. The Update operation enables users to modify an existing connection by specifying its ID and providing a JSON request body with the updated fields.

Typical use cases include automating updates to connection configurations in Kobana, such as changing credentials, endpoints, or other connection parameters without manual intervention. For example, if you need to update connection details after rotating credentials or modifying access settings, this node operation can perform that update programmatically within an n8n workflow.

Properties

Name Meaning
ID The unique identifier of the connection resource to update.
Additional Fields A JSON object containing any extra fields to include in the request (optional).
Request Body The JSON-formatted request body containing the fields and values to update on the connection. This is required and must be valid JSON.

Output

The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated connection object with its current state and properties as confirmed by the API.

  • The output is structured as an array of JSON objects, each representing the updated resource.
  • No binary data output is produced by this operation.

Dependencies

  • Requires an active Kobana API credential configured in n8n for authentication.
  • The node dynamically selects the API base URL depending on the environment (production or sandbox).
  • The API requests are made over HTTP(S) with appropriate method and endpoint based on the resource and operation.

Troubleshooting

  • Invalid JSON in Request Body: If the JSON provided in the "Request Body" field is malformed, the node will throw a parsing error. Ensure the JSON syntax is correct before running.
  • Missing or Incorrect ID: The "ID" property is mandatory. Omitting it or providing an invalid ID will cause the API to return an error indicating the resource was not found.
  • Authentication Errors: If the API key or credentials are incorrect or expired, the node will fail with an authentication error. Verify the Kobana API credentials in n8n.
  • API Endpoint Errors: If the resource or operation is not supported or the API endpoint changes, errors may occur. Confirm the resource and operation names match those supported by the Kobana API version used.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion