🌎📥 Load Global Pick Me

Big ComfyUI graphs turn into spaghetti fast, and one recurring source of the mess is dragging a single text value to five different places across a sprawling canvas. Bjornulf's "Global" nodes sidestep that by connecting things through a shared ID string instead of a literal wire. This is the read side of that pattern for text: give it the same global_pickme_id that a Global Write Pick Me node somewhere else in your graph is using, and it picks up that value - no noodle required, however far apart the two nodes are on the canvas.

How it works

It's the same idea as the pack's Global Variables nodes (Save/Load Global Variables), just scoped to the "Pick Me" chain pattern specifically rather than general variable storage. Set global_pickme_id to match a Write node elsewhere, and this node resolves to whatever that write node currently holds. According to the pack's own docs, it can also automatically return a random value from the list associated with that ID - so depending on how the corresponding write side is set up, you might get a fixed pick or a randomized one from a pool, without any extra wiring on the read side.

Inputs and outputs

One required input: global_pickme_id, a STRING defaulting to default - this is the only thing that has to match between the write and read ends of the pair; get it wrong (a typo, mismatched capitalization) and the two nodes simply won't be talking to each other, silently. Three outputs: picked_text (the resolved value), picked_text_as_variable (formatted for use as a <name> style variable reference elsewhere in the pack's Advanced Write Text syntax, if that's how you're using it), and random - a second, independently randomized pick from the same pool.

Installing it

Ships with the rest of Bjornulf_custom_nodes. ComfyUI Manager → search "Bjornulf_custom_nodes" → install → restart, or clone manually: cd ComfyUI/custom_nodes && git clone https://github.com/justUmen/Bjornulf_custom_nodes, then restart. No extra dependency for this specific node - it's in-memory/graph-state bookkeeping, not I/O.

Common issues & troubleshooting

The single biggest trap with any ID-based linking pattern like this: silent mismatch. If global_pickme_id on this node doesn't exactly match the ID on the corresponding Global Write Pick Me node, you won't get an error - you'll just get a default or empty value, and it's not always obvious why. If this node isn't returning what you expect, the first thing to check is a character-for-character comparison of the ID string on both ends, not the wiring (there isn't any to check).

Because the connection is invisible on the canvas, this pattern trades a spaghetti-graph problem for a different kind of confusion: it's easy to forget which nodes are secretly linked by ID when you come back to a workflow weeks later, especially in a large graph with several different global IDs in play. If you lean on this heavily, it's worth a habit of labeling these nodes clearly (ComfyUI lets you rename any node) with the ID they're using, so a future read-through of the graph doesn't require hunting down every Write node to figure out what's actually feeding this one.