TellzmInstall

Summary

Calls the Tellzm MCP tool transition_form_process_instance for a form-process instance, requiring the forms.write scope. The UI exposes a "New Status" admin override, but the handler doesn't send that value (see notes).

Inputs

• Workspace Name or ID — Selects which authorized workspace to target. It is sent as the x-tellzm-workspace-slug header. Options are loaded from the credential's allowed workspaces.
• Instance ID (required) — The id of the form-process instance to transition.
• New Status (required) — Choices are Running, Completed, Rejected or Cancelled (default Running). It is shown as an admin status override. The source never reads it, so it isn't sent to the API.

Output shape

One output item per input item. Its JSON is the parsed result returned by the transition_form_process_instance MCP tool, typically the updated instance.

The handler reads newStatus nowhere. It sends only instanceId, plus nodeRef if that parameter is set. nodeRef has no UI field for this operation, so it is normally omitted. The selected New Status therefore probably has no effect, and the server decides what transition happens. Test before relying on it to set a specific status. The call fails early if the credential lacks the forms.write scope. MCP errors, a 401, or a rate limit that persists after one retry raise a node error.

Examples

Example 1: Move a form-process instance to another status from an n8n workflow, using the instance id from an earlier step.

Resource: Form-Process, Operation: Transition, Instance ID: {{$json.instanceId}}, New Status: Completed. Verify the resulting status in the output, since the handler doesn't send New Status.

Links

• n8n community nodes installation guide