TellzmInstall

Summary

Calls any Tellzm MCP tool by name with a JSON arguments object, as an escape hatch for tools the node's other resources don't expose. Sends a JSON-RPC tools/call request to the Tellzm /mcp endpoint and returns the parsed result.

Inputs

• Workspace Name or ID (workspaceSlug) — Workspace to target, chosen from the workspaces the credential is authorized for. If set, it is sent as the x-tellzm-workspace-slug header.
• Tool Name (tool) (required) — MCP tool name in snake_case, e.g. list_projects (the default). The full catalog is at https://tellzm.com/docs/mcp or /mcp/catalog.
• Arguments (JSON) — JSON object passed as the tool's arguments, e.g. { "taskId": "abc" }. Defaults to {}.

Output shape

One output item per input item. Its json is the tool's result: the first text content block of the MCP response, parsed as JSON.

If the tool returns text that isn't valid JSON, json is that raw string. An empty result gives null. List-style results are not split into separate items; the whole payload stays in one item. MCP errors, tool errors (isError) and a 401 throw a node error. A 429 or 503 is retried once after a delay. Unlike the other resources, this operation runs no client-side scope check and sends no idempotency key, so the server enforces permissions and repeated calls may repeat side effects.

Examples

Example 1: List all projects in a specific workspace

Workspace: choose one; Tool Name: list_projects; Arguments: {}

Example 2: Fetch a single task by id using a tool name typed directly

Tool Name: get_task; Arguments: { "taskId": "{{$json.taskId}}" }

Links

• n8n community nodes installation guide