Belake.aiInstall

Summary

Update an existing Belake.ai tool by ID, sending a PATCH request with the selected HTTP or MCP tool type and only the update fields you add. HTTP tools can update request settings and metadata; MCP tools can update server, transport, authentication, timeout, selected tools, and metadata.

Inputs

• Tool ID (required) — Identifier of the tool to update.
• Tool Type (required) — Choose HTTP or MCP; this is included in the update request.
• HTTP update fields — Add any fields to change: name, description, docstring, method, URL, auth type, body, headers, or parameter sets. Header entries with a name become a key-value object; parameter entries with non-empty JSON text are sent as a list of strings. Adding Headers or Param Sets with no usable entries sends an empty object or list, respectively.
• MCP update fields — Add any fields to change: name, description, docstring, server URL, transport type, auth type, timeout, auth config, or selected tools. Auth config entries with a name become a key-value object; selected tool names are sent as a list. Adding either collection with no usable entries sends an empty object or list.

Output shape

One n8n item per input item, containing the API response in its json field.

The request uses PATCH /v1/tools/{toolId}. The request body always includes the selected tool type; fields not added to the update collection are omitted. Requires Belake.ai API credentials. With Continue On Fail enabled, a failed item returns {"error":"..."} in its json field.

Links

• n8n community nodes installation guide