ComfyUI Node

End Anything

Return one value of any type from a sub-workflow, under a name you pick

By heshengtao·Created 2 years ago·Updated 7 days ago· 2,321
End Anything
  • any
    key

    End Workflow, this pack's node for closing out a sub-workflow, only takes images and text. End Anything is the generalized version - it accepts a single input of any type at all (the any port is a genuine wildcard) and pairs it with a key, a name you choose to identify it by. Same job, fewer assumptions about what you're actually returning.

    Why this exists

    This pack lets you treat an entire workflow as a callable sub-routine: an outer graph's "workflow transfer" node can hand a saved inner workflow off to a second ComfyUI instance, run it, and read results back once it's done. End Workflow covers the common case - images and text coming back out. But this pack builds LLM agent pipelines, and agent pipelines produce all kinds of intermediate values that aren't images or text specifically - a latent, a mask, a number, a custom object from one of this pack's own model types. End Anything is what you reach for when the thing you need to hand back to the calling workflow doesn't fit the fixed images/text shape, or when you specifically want to label what's coming back rather than rely on positional inputs.

    The inputs and outputs that matter

    Two required fields, and that's the entire node:

    • key (STRING) - the name you're returning this value under. This is what lets the calling workflow ask for a specific result by name rather than guessing based on type or position, especially useful if a sub-workflow needs to hand back more than one thing.
    • any (*) - the value itself, of whatever type. This is a genuine wildcard input - ComfyUI's * type accepts a connection from any output socket, which is what makes this node usable regardless of what your sub-workflow actually produces.

    No outputs. Like End Workflow, this is a terminal node, marked as an output node so it executes on its own even without anything downstream to consume from it - its job is to make any's value available to whatever called the workflow it lives in, not to pass a value further along inside its own graph.

    Installing it

    Ships with the pack:

    • ComfyUI Manager: search "comfyui_LLM_party", install, restart.
    • Manual: cd ComfyUI/custom_nodes && git clone https://github.com/heshengtao/comfyui_LLM_party, then pip install -r requirements.txt from inside the pack folder using ComfyUI's Python, then restart.

    Common issues & troubleshooting

    Wired something in, but the calling workflow doesn't seem to receive it correctly. Check the key you set matches what the outer workflow's transfer node is actually asking for - since retrieval is keyed by this string rather than by position or type, a typo or mismatched key is the most likely reason a value silently doesn't show up where you expect.

    Not sure whether to use this or End Workflow. If what you're returning is genuinely an image and/or some text, End Workflow is the simpler, more purpose-built choice - it's specifically shaped for that case. Reach for End Anything when you need to return something else, or more than one differently-typed thing, or want an explicit name attached to what's coming back rather than relying on a fixed images/text shape.

    The sub-workflow mechanism itself isn't returning anything at all. That's more likely a problem with how the inner workflow was saved or referenced than with this node specifically - confirm it was saved into the pack's workflow_api folder and that the outer workflow's transfer node is pointed at the right saved workflow before assuming the End Anything node itself is misconfigured.

    Category大模型派对(llm_party)/工作流(workflow)

    Inputs (2)

    NameTypeDefaultDescription
    keySTRING
    any*

    Outputs (0)

    No outputs