Nodes/Bjornulf_custom_nodes/๐ŸŒŽโœ’๐Ÿ‘‰ Global Write Pick Me
ComfyUI Node

๐ŸŒŽโœ’๐Ÿ‘‰ Global Write Pick Me

Switch prompts by name, no wires needed

By justUmenยทCreated 2 years agoยทUpdated about a year agoยท 545
๐ŸŒŽโœ’๐Ÿ‘‰ Global Write Pick Me
    • text
    โ—„global_pickme_iddefaultโ–บ
    โ—„pickedfalseโ–บ
    โ—„textโ€”โ–บ

    This is the same idea as the pack's Write Pick Me Chain node - several text nodes, one active at a time, switchable with a click - except it drops the requirement that they all be physically wired together. Instead of chaining nodes with cables, you give a group of Global Write Pick Me nodes the same global_pickme_id string, and ComfyUI treats them as a set no matter where they sit in your graph. No spaghetti required.

    It's one of the pack's identifier-based tools, part of justUmen's sprawling Bjornulf_custom_nodes collection, and it pairs with a sibling read-side node - Load Global Pick Me - that pulls the active value back out anywhere else in your workflow, again just by matching the id, with no cable between them either.

    How it works

    Set global_pickme_id to some name you choose - "intro_prompt", "scene_a", whatever's meaningful to you - on however many Global Write Pick Me nodes you want grouped together, even if they're scattered across different parts of a large workflow. Only one node sharing that id is meant to be "picked" (active) at a time; toggling picked on one is what the node's UI button does, similar to the chain version. Anywhere else in the workflow, drop a Load Global Pick Me node with the matching id, and it retrieves whichever value is currently active. Worth knowing: Load Global Pick Me also has a fallback behavior the chain version doesn't mention - if nothing's explicitly picked, it will automatically return a random value from the pool of nodes sharing that id, so it can double as a lightweight randomizer between named options, not just a manual switch.

    The inputs and outputs that matter

    • global_pickme_id (default "default") - the shared name that groups nodes together. Change it per group; leave nodes on "default" only if you genuinely want them all in the same pool.
    • picked (default false) - whether this node is the currently active one for its id. Mostly toggled via the node's button rather than set directly.
    • text (required, multiline) - the candidate prompt this specific node holds.

    One output: text, the STRING for this node - though in practice you'll more often be reading the active value for a given id through the companion Load Global Pick Me node elsewhere in your graph, rather than wiring this node's own output directly.

    How to install it

    ComfyUI Manager: search "Bjornulf_custom_nodes," install, restart. Manual install:

    cd ComfyUI/custom_nodes
    git clone https://github.com/justUmen/Bjornulf_custom_nodes
    

    then restart. No special dependency beyond core ComfyUI for this node - the pack's requirements.txt (ollama, ffmpeg-python, opencv-python, and more) is for the video/TTS/AI side of the pack, not this one.

    Common issues & troubleshooting

    Typos in the id silently split your group in two. Since grouping is purely string-matching on global_pickme_id, a stray space or a slightly different name means two nodes you meant to be in the same pool aren't. There's no validation catching this for you - if switching one node doesn't seem to affect the others you expected it to, check the id strings match exactly.

    Leaving everything on "default". It's an easy trap in a big workflow: if you never bother renaming the id, every Global Write Pick Me node you add ends up in the same pool by accident, and clicking PICK ME on one deactivates prompt nodes you didn't mean to touch. Name your ids deliberately once you have more than one group in play.

    Expecting deterministic output when nothing's picked. Because Load Global Pick Me falls back to a random pick from the pool when nothing is explicitly active, a workflow can look "randomly" inconsistent between runs if you forgot to actually pick one - that's the node behaving as documented, not a bug, but it's easy to mistake for one if you didn't know the fallback existed.

    Between the two Pick Me variants, the chain version is more explicit (you can see the connections), while this one scales better across a large, sprawling workflow where dragging wires across the canvas isn't practical.

    CategoryBjornulf

    Inputs (3)

    NameTypeDefaultDescription
    global_pickme_idSTRINGdefaultโ€”
    pickedBOOLEANfalseโ€”
    textSTRINGโ€”

    Outputs (1)

    NameTypeDescription
    textSTRINGโ€”