工作流上传

Despite the name - 工作流上传, "workflow upload" - this node uploads nothing anywhere. It's the bouncer at the door of the whole ComfyUI-RemoteCall pipeline: you paste a workflow's JSON into it, it tells you whether that's even a workflow, and it hands a clean compacted copy to the rest of the chain. Think of it as the paste-and-validate gatekeeper you run before you ship anything across the network to another machine.

Why it exists

RemoteCall runs a workflow on a different ComfyUI instance, which means the workflow has to exist as text in your graph first. But pasting a thousand-line JSON blob straight into a submission node is how you end up debugging a typo at 1am. This node gives you a two-second sanity check - is it valid JSON, and does it look like a workflow at all? - and normalizes it into the form the other nodes want.

How it works

You feed it 工作流_JSON (a multiline text box, the only input). It JSON-parses the string and, if that succeeds, counts nodes. It recognizes both of ComfyUI's workflow shapes:

• the UI format you get from File → Save (a root object with a nodes array), or
• the API format ComfyUI's /prompt endpoint actually consumes (a dict of node_id: {class_type, inputs}, possibly wrapped in a prompt key).

Either way it just needs parseable JSON that looks like a workflow - this node is format-agnostic. The stricter API-format gate lives in the sibling 工作流解析 (Workflow Parse) node.

The outputs

• 是否有效 (BOOLEAN) - the verdict.
• 工作流_JSON (STRING) - the workflow re-serialized compactly (non-ASCII text is preserved, which matters if your prompts are in anything but English). This is the wire you run to 上传提交 or into 工作流解析.
• 节点数 (INT) - how many nodes it counted; a quick smell test.
• 消息 (STRING) - OK on success, or the reason it failed.

Installing it

Same pack as the rest: ComfyUI-RemoteCall. ComfyUI Manager → Install Custom Nodes → search ComfyUI-RemoteCall (or 远程调用), restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/playboy-dongan/ComfyUI-RemoteCall

Dependencies are requests and av, both of which a normal ComfyUI already has. No model downloads - nothing heavy here.

When it's not OK

Two failure modes, both readable in 消息: paste nothing and you get 内容为空; paste broken JSON and you get JSON 解析失败: <the error>, which will point you at the exact character. The subtler one is 节点数 coming back 0 - the JSON parsed fine but doesn't match either workflow shape, so what you pasted isn't a ComfyUI workflow export. That's usually a copy from the wrong place in the UI.

One honest note: as the entry point it's near-useless on its own, but that's fine. Its job is to be the boring, reliable first link in the chain - paste, validate, compact, pass on.