Nodes/RunningHub/RH Split Output URLs
ComfyUI Node

RH Split Output URLs

RH Split Output URLs turns one messy text block into five clean sockets

By liangzheng1128·Created 3 months ago·Updated 3 months ago· 0
RH Split Output URLs
    • url1
    • url2
    • url3
    • url4
    • url5
    output_urls

    Somewhere in a RunningHub workflow there's a node that spits out a block of text with five image URLs on five lines. ComfyUI, meanwhile, would like those as five separate wires. RH Split Output URLs is the translator: one multiline output_urls input in, up to five individual string outputs out, split on newlines.

    This is a "completing the graph" node, not a glamorous one, and that's fine - the plumbing layer is where most workflows actually live. You'll reach for it in two situations:

    • After RH Task Outputs, which returns all result URLs joined into one newline-separated output_urls string. Feed that block into this node, and each URL gets its own socket to route onward.
    • After any Model node (video/audio outputs) whose video_url or audio_url comes back as a plain string. If you expect more than one output URL, this is the clean way to fan them out.

    Each line becomes url1, url2, url3, url4, url5. Fewer than five lines and the leftovers are empty strings - so the last sockets just sit there empty, which downstream nodes usually read as "nothing here." More than five lines and the extra ones are dropped, which is the one real trap: if your workflow produces six images, you only get the first five. Check the count before you rely on all outputs.

    The two inputs that matter

    Just one, honestly:

    • output_urls (STRING, multiline) - newline-separated URLs. Paste or wire.

    That's it. No API key, no network calls - a local utility that works even with zero RunningHub setup, so it's safe to use in any graph whether or not you ever touch the cloud half of the pack.

    How it's useful in the typical flow

    The pack's README shows the canonical chain as RH Settings → RH Node Info → RH Execute Workflow → RH Download Image. In practice, Execute Workflow already splits its outputs into output_url1 through output_url5 on its own, so you don't need this node there. Where Split Output actually earns its keep is converting a string of URLs - from RH Task Outputs or a hand-pasted list - into the individual sockets that RH Download Image or RH Download Video can grab one at a time:

    RH Task Outputs (output_urls) → RH Split Output URLs → url1 → RH Download Image
                                                         └→ url2 → RH Download Image
    

    Install

    Ships with the ComfyUI-RunningHub pack:

    cd ComfyUI/custom_nodes/
    git clone https://github.com/liangzheng1128/ComfyUI-RunningHub
    cd ComfyUI-RunningHub
    pip install -r requirements.txt
    

    or install via ComfyUI Manager by searching "RunningHub". Restart, and it's under RunningHub/Utils. Dependencies are the pack's usual light set - requests, websocket-client, Pillow, numpy. No models to download, no key required, just split and route.

    CategoryRunningHub/Utils

    Inputs (1)

    NameTypeDefaultDescription
    output_urlsSTRINGNewline-separated URLs

    Outputs (5)

    NameTypeDescription
    url1STRING
    url2STRING
    url3STRING
    url4STRING
    url5STRING