Subworkflow (from URL)

Subworkflow (from URL) (class SWF_SubworkflowFromURL) is the sibling of the main Subworkflow node from the eniewold/ComfyUI-Subworkflow pack - same behavior, one difference: instead of picking a workflow from a local dropdown, you paste a URL and it fetches the workflow JSON from there. It's the variant you reach for when the reusable pipeline shouldn't have to live on every machine that wants to run it.

The author's own framing is a (private or public) library of workflows served from a central repo or website. Team workflow, basically: one person maintains the inner workflow, everybody else's Subworkflow nodes pick up the change on the next run. It also pairs naturally with git - point the node at a raw GitHub URL for a workflow file and you get version control over your reusable pipeline for free.

Inputs that matter

• url - the absolute http:// or https:// URL returning a workflow JSON. It has to be the raw JSON, not an HTML page wrapping it. The node handles both UI-format and API-format workflows, same as the file loader.
• verify SSL (verify_ssl, default on) - controls HTTPS certificate validation. The README is specific about why this exists: Python SSL certificate issues on certain endpoints, GitHub raw URLs included. If the load fails with a certificate error, flipping this off usually fixes it.
• at execution (reload_each_execution, default reload) - same as the file node: reload the URL every run, or cache the loaded workflow. Keep the default if the inner workflow is being actively edited.

Outputs are dynamic, inferred from the inner workflow's Subworkflow Output nodes.

Install

Identical to the rest of the pack - ComfyUI Manager, search "Subworkflow (reuseable workflows)", or:

cd ComfyUI/custom_nodes
git clone https://github.com/eniewold/ComfyUI-Subworkflow.git

Restart ComfyUI, hard-refresh the browser. No extra pip dependencies; it does need a recent ComfyUI (0.18.x) for the V3 node API it's built on.

The part to take seriously

This node executes whatever JSON the URL returns. That's the feature and the risk. ComfyUI custom nodes already run arbitrary code on your machine (the ecosystem's security history is not hypothetical), and this extends that trust to a remote file - so only point it at sources you control or genuinely trust. The verify SSL switch is a convenience for flaky cert chains, not a substitute for knowing what you're fetching. Keep it on for anything you didn't write.

Aside from that, expect the same beta quirks as the main node: undetermined slot ordering, silent link severing on type mismatch, progress bars that overshoot. And remember the sharing caveat cuts the other way here - a URL-based inner workflow is fetched fresh each run, so if the endpoint goes away, every workflow depending on it breaks at once. A local file at least fails loudly at load time instead of vanishing under you.