Prop From Properties

Every structured-data workflow ends up in the same place: you've collected a bunch of name/value pairs and now you need to extract one of them by name. Prop From Properties is the extraction half of TinyBee's property system. Give it a TINYPROPS bundle and a property name, and it hands you the property itself, its value, and its type.

This node only makes sense inside the pack's own properties ecosystem, so here's the shape of it: TinyBee lets you build a bundle of typed name/value pairs with its encode/combine property nodes, attach that bundle to saved images (via Save Image w/Meta), and read it back later. Prop From Properties is the moment you stop carrying the whole bag around and pull out exactly the one value you need. It's the pack's answer to "give me this key out of this dictionary," with a type tag thrown in so downstream logic knows what it's dealing with.

How it works

It looks up property_name inside the properties dictionary. If found, it returns three things:

• property (TINYPROP) - the full property object, name and type intact.
• value (*) - the actual value, whatever type it is. This is the one you'll usually wire onward.
• value_type (STRING) - the recorded type tag, like INT, FLOAT, STRING, OBJECT, LIST, JSON, or NULL. Feed this to a switch or compare node and you can branch on what kind of data came back.

If the key isn't in the bundle, you get a NULL type and an empty value rather than a crash - which means you should check value_type before using the result, or your workflow will silently carry an empty value downstream.

Inputs: properties (TINYPROPS, the bundle) and property_name (STRING). Outputs: property, value, value_type.

Installing it

Prop From Properties ships in ComfyUI-TinyBee, the small MIT-licensed utility pack from TinyBeeman. No models, no heavy deps. Via Manager:

1. ComfyUI Manager → Custom Nodes Manager.
2. Search "ComfyUI-TinyBee" and install.
3. Restart ComfyUI.

Or clone:

cd ComfyUI/custom_nodes
git clone https://github.com/TinyBeeman/ComfyUI-TinyBee

Restart and it's under 🐝TinyBee/Util. Standard library only - the pack's jsonata dependency is for its JSON Parser node, nothing else.

Gotchas

The TINYPROPS type is pack-specific: only TinyBee's own property nodes produce it, and other packs won't speak it. If you're feeding this node from outside the TinyBee property chain, you'll need to convert your data into that format first. Also keep the missing-key behavior in mind - a typo in property_name doesn't error, it just returns NULL. And note the value output is the wildcard type (*), so ComfyUI will let you wire it almost anywhere; whether the downstream node can actually use it depends on what type the property was encoded as.