π§Ύ Female Outfit Inputs From JSON
Decode a JSON Object Into Outfit Pins
- preset
- age_group
- race
- body_type
- pose
- background
- mood
- time_of_day
- weather
- color_scheme
- description_style
- creative_scale
- character_name
- custom_attributes
- avoid_terms
- arm
- cheeks
- ear
- eyewear
- feet
- fingers
- forearm
- forehead
- hairstyle
- hand
- headgear
- legs
- lips
- neck
- nose
- torso
- waist
- makeup_data
- inputs_json
If you've read the male version of this node, this is the same thing on the women's rack: Female Outfit Inputs From JSON (class FemaleOutfitInputsFromJSONNode, in π Outfit/Helpers/Female) takes one JSON object and expands it into individual STRING outputs you can wire into FemaleOutfitNode. It's a decoder with defaults, and it exists so the outfit node can be driven by data instead of dropdown clicks - whether the JSON comes from your own script or from the pack's own helper chain (Photo Style Helper β Preset Patch Applier β here).
The inputs and outputs
Single required input: merged_json (multiline STRING). Paste a JSON object in, and it maps each key to a matching output pin - the style fields (preset, age_group, race, body_type, pose, background, mood, time_of_day, weather, color_scheme, description_style, creative_scale, character_name, custom_attributes, avoid_terms), then the female attire parts (arm, cheeks, ear, eyewear, feet, fingers, forearm, forehead, hairstyle, hand, headgear, legs, lips, neck, nose, torso, waist), then makeup_data and inputs_json.
Two behaviors matter. Missing keys don't error - selectors come out as random (so a partial patch still yields a full outfit) and freeform fields come out empty. And inputs_json is a pass-through of the original string, so you can keep the raw JSON flowing on a single wire.
Wiring it up
Each output plugs into the same-named input on FemaleOutfitNode; leave pins unwired when you don't care about them. The gender mismatch trap is real here: this node emits cheeks and lips (which the female node expects) and no facial_hair - feed it male-shaped JSON and those male keys silently fall back to random.
Install
Same as every node in this pack - ComfyUI Manager, search "ComfyUI Outfit Selection", or:
cd ComfyUI/custom_nodes/
git clone https://github.com/manifestations/comfyui-outfit.git
Restart ComfyUI. It's stdlib-only JSON parsing: no dependencies, no models, no Ollama required. The only real failure mode is malformed JSON, which it swallows and treats as empty (read: everything random), so if your outfit suddenly stops honoring your patches, validate the JSON string first - that's the silent trap.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| merged_json | STRING | β |
Outputs (34)
| Name | Type | Description |
|---|---|---|
| preset | STRING | β |
| age_group | STRING | β |
| race | STRING | β |
| body_type | STRING | β |
| pose | STRING | β |
| background | STRING | β |
| mood | STRING | β |
| time_of_day | STRING | β |
| weather | STRING | β |
| color_scheme | STRING | β |
| description_style | STRING | β |
| creative_scale | STRING | β |
| character_name | STRING | β |
| custom_attributes | STRING | β |
| avoid_terms | STRING | β |
| arm | STRING | β |
| cheeks | STRING | β |
| ear | STRING | β |
| eyewear | STRING | β |
| feet | STRING | β |
| fingers | STRING | β |
| forearm | STRING | β |
| forehead | STRING | β |
| hairstyle | STRING | β |
| hand | STRING | β |
| headgear | STRING | β |
| legs | STRING | β |
| lips | STRING | β |
| neck | STRING | β |
| nose | STRING | β |
| torso | STRING | β |
| waist | STRING | β |
| makeup_data | STRING | β |
| inputs_json | STRING | β |