Nodes/PRYX ComfyUI Higgsfield/PRYX ComfyUI Higgsfield Reference Collector
ComfyUI Node

PRYX ComfyUI Higgsfield Reference Collector

Turn up to 30 images into one ordered reference list

By PRYX-STUDIO·Created 24 days ago·Updated 11 days ago· 2
PRYX ComfyUI Higgsfield Reference Collector
  • references
  • image
  • video
  • audio
  • image_2
  • image_3
  • image_4
  • image_5
  • image_6
  • image_7
  • image_8
  • image_9
  • image_10
  • image_11
  • image_12
  • image_13
  • image_14
  • image_15
  • image_16
  • image_17
  • image_18
  • image_19
  • image_20
  • image_21
  • image_22
  • image_23
  • image_24
  • image_25
  • image_26
  • image_27
  • image_28
  • image_29
  • image_30
  • video_2
  • video_3
  • video_4
  • video_5
  • video_6
  • video_7
  • video_8
  • video_9
  • video_10
  • audio_2
  • audio_3
  • audio_4
  • audio_5
  • audio_6
  • audio_7
  • audio_8
  • audio_9
  • audio_10
  • references
◄external_url►
◄external_typeurl►
◄label►
◄names►

Multimodal video models eat references. Kling wants your character and your outfit. Wan 3.0's reference endpoint wants image 1, image 2, a video reference and maybe an audio track, and it addresses them by number in the prompt. Feeding five separate wires into a generator and hoping it guesses the order is how you get the wrong face on the right body.

The Reference Collector is the node that fixes that: one socket in the graph, a list of media in a defined order, and a generator that reads them in exactly the order you built.

How it works

It builds a references value - the pack's own PRYX_HF_REFERENCES type - from every socket you connect. Slot counts:

  • image … image_30 - 30 image slots, and image batches are split, so a 4-image batch from one Load Image becomes four ordered references.
  • video … video_10 - 10 video slots.
  • audio … audio_10 - 10 audio slots.
  • references - merge an existing collection in, if you have one already.
  • external_url + external_type (url or file) - one already-public HTTPS link to a document or web page.

Order is deterministic and not the order you drew the wires. Slots are collected in numeric order: image_2 always comes after image, even if you connected image_2 first. Direct inputs on the generator (its image, video, audio, end_image sockets) map before anything coming from a Collector, and all of it is numbered separately per media type. Two Collector images become Image 1 and Image 2; they don't shift the videos.

The frontend grows extra sockets as you connect them, so you're not staring at 50 empty dots on drop.

The two fields you'll actually touch are names and label. names takes one assignment per line:

image_1=person
image_2=outfit
video_1=camera

Those become labels. Labels are what the {{ref:label}} prompt syntax resolves against, but only on endpoints that document numbered prompt tokens - currently Wan 3.0 Reference to Video. On other endpoints named aliases are rejected outright rather than silently ignored, which is the honest failure mode: better a stopped request than a wrong one. Braces aren't allowed in names, duplicate keys are an error, and labels must be unique per media item.

label is the legacy single-label field kept so old workflows still open. Use names for anything new.

Output

One output: references. Wire it into the references input of a generator (Text to Video, Image to Video, Reference to Video, Image Generate & Edit, Video Edit, Video Extend) or into Reference Preview. Model limits - how many references that endpoint accepts and of which type - are checked by the generator, not here. The Collector will happily build you eight images for a model that allows two; you'll get a validation error before anything uploads.

Install

Manager: search PRYX ComfyUI Higgsfield, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/PRYX-STUDIO/pryx-comfyui-higgsfield.git pryx-comfyui-higgsfield
python -m pip install -r pryx-comfyui-higgsfield/requirements.txt

Portable Windows: .\python_embeded\python.exe -m pip install -r .\pryx-comfyui-higgsfield\requirements.txt. ComfyUI 0.35.0+, frontend 1.53.6+, Python 3.10–3.13. No model downloads - just higgsfield-client, httpx and jsonschema. Your Higgsfield key goes in Settings → PRYX ComfyUI Higgsfield → Credentials (key-id:key-secret), or via HF_KEY for headless.

Note that the collector itself never uploads anything. Uploads happen later, in the generator: local media gets converted, pushed through Higgsfield's presigned upload flow, and only then referenced by URL. That's why an estimate-only run can still touch the network.

Traps worth knowing

  • external_url must be public HTTPS already. Everything else in this node is a local file the pack will upload for you - that one field is not.
  • Reordering means renumbering. Move a reference to a slot you think is earlier and you may have changed nothing; the Preview node shows the real mapping. Run it after touching media, labels or the model.
  • The model still has the final say. A video-only reference type on an image-only endpoint fails validation before upload, not after you've paid for anything.
CategoryPRYX/ComfyUI/Higgsfield

Inputs (55)

NameTypeDefaultDescription
referencesoptPRYX_HF_REFERENCES—
imageoptIMAGE—
videooptVIDEO—
audiooptAUDIO—
external_urloptSTRING—
external_typeoptCOMBOurl2 options: url, file
labeloptSTRINGLegacy shared label. Prefer names for separate media labels. Existing workflows retain this label.
namesoptSTRINGOptional names, one per line: image_1=person, image_2=outfit, video_1=camera. Otherwise socket names become labels. Batches use name[1], name[2], etc. Reference Preview shows the final mapping.
image_2optIMAGEImage slot 2. Slots are collected in numeric order, not connection order. Model limits still apply.
image_3optIMAGEImage slot 3. Slots are collected in numeric order, not connection order. Model limits still apply.
image_4optIMAGEImage slot 4. Slots are collected in numeric order, not connection order. Model limits still apply.
image_5optIMAGEImage slot 5. Slots are collected in numeric order, not connection order. Model limits still apply.
image_6optIMAGEImage slot 6. Slots are collected in numeric order, not connection order. Model limits still apply.
image_7optIMAGEImage slot 7. Slots are collected in numeric order, not connection order. Model limits still apply.
image_8optIMAGEImage slot 8. Slots are collected in numeric order, not connection order. Model limits still apply.
image_9optIMAGEImage slot 9. Slots are collected in numeric order, not connection order. Model limits still apply.
image_10optIMAGEImage slot 10. Slots are collected in numeric order, not connection order. Model limits still apply.
image_11optIMAGEImage slot 11. Slots are collected in numeric order, not connection order. Model limits still apply.
image_12optIMAGEImage slot 12. Slots are collected in numeric order, not connection order. Model limits still apply.
image_13optIMAGEImage slot 13. Slots are collected in numeric order, not connection order. Model limits still apply.
image_14optIMAGEImage slot 14. Slots are collected in numeric order, not connection order. Model limits still apply.
image_15optIMAGEImage slot 15. Slots are collected in numeric order, not connection order. Model limits still apply.
image_16optIMAGEImage slot 16. Slots are collected in numeric order, not connection order. Model limits still apply.
image_17optIMAGEImage slot 17. Slots are collected in numeric order, not connection order. Model limits still apply.
image_18optIMAGEImage slot 18. Slots are collected in numeric order, not connection order. Model limits still apply.
image_19optIMAGEImage slot 19. Slots are collected in numeric order, not connection order. Model limits still apply.
image_20optIMAGEImage slot 20. Slots are collected in numeric order, not connection order. Model limits still apply.
image_21optIMAGEImage slot 21. Slots are collected in numeric order, not connection order. Model limits still apply.
image_22optIMAGEImage slot 22. Slots are collected in numeric order, not connection order. Model limits still apply.
image_23optIMAGEImage slot 23. Slots are collected in numeric order, not connection order. Model limits still apply.
image_24optIMAGEImage slot 24. Slots are collected in numeric order, not connection order. Model limits still apply.
image_25optIMAGEImage slot 25. Slots are collected in numeric order, not connection order. Model limits still apply.
image_26optIMAGEImage slot 26. Slots are collected in numeric order, not connection order. Model limits still apply.
image_27optIMAGEImage slot 27. Slots are collected in numeric order, not connection order. Model limits still apply.
image_28optIMAGEImage slot 28. Slots are collected in numeric order, not connection order. Model limits still apply.
image_29optIMAGEImage slot 29. Slots are collected in numeric order, not connection order. Model limits still apply.
image_30optIMAGEImage slot 30. Slots are collected in numeric order, not connection order. Model limits still apply.
video_2optVIDEOVideo slot 2. Slots are collected in numeric order, not connection order. Model limits still apply.
video_3optVIDEOVideo slot 3. Slots are collected in numeric order, not connection order. Model limits still apply.
video_4optVIDEOVideo slot 4. Slots are collected in numeric order, not connection order. Model limits still apply.
video_5optVIDEOVideo slot 5. Slots are collected in numeric order, not connection order. Model limits still apply.
video_6optVIDEOVideo slot 6. Slots are collected in numeric order, not connection order. Model limits still apply.
video_7optVIDEOVideo slot 7. Slots are collected in numeric order, not connection order. Model limits still apply.
video_8optVIDEOVideo slot 8. Slots are collected in numeric order, not connection order. Model limits still apply.
video_9optVIDEOVideo slot 9. Slots are collected in numeric order, not connection order. Model limits still apply.
video_10optVIDEOVideo slot 10. Slots are collected in numeric order, not connection order. Model limits still apply.
audio_2optAUDIOAudio slot 2. Slots are collected in numeric order, not connection order. Model limits still apply.
audio_3optAUDIOAudio slot 3. Slots are collected in numeric order, not connection order. Model limits still apply.
audio_4optAUDIOAudio slot 4. Slots are collected in numeric order, not connection order. Model limits still apply.
audio_5optAUDIOAudio slot 5. Slots are collected in numeric order, not connection order. Model limits still apply.
audio_6optAUDIOAudio slot 6. Slots are collected in numeric order, not connection order. Model limits still apply.
audio_7optAUDIOAudio slot 7. Slots are collected in numeric order, not connection order. Model limits still apply.
audio_8optAUDIOAudio slot 8. Slots are collected in numeric order, not connection order. Model limits still apply.
audio_9optAUDIOAudio slot 9. Slots are collected in numeric order, not connection order. Model limits still apply.
audio_10optAUDIOAudio slot 10. Slots are collected in numeric order, not connection order. Model limits still apply.

Outputs (1)

NameTypeDescription
referencesPRYX_HF_REFERENCES—