Magnific Creation Picker
Reuse something you already made, without leaving ComfyUI
- image
- video
- audio
- creation_identifier
- metadata
Here's a workflow that's genuinely annoying to do by hand: you liked an image you made in Magnific last week, and you want it as the reference for something you're generating now. Normally that's download, find the file, drag it into ComfyUI, hope the size is right.
This node skips all of that. Browse your Magnific projects from inside the graph, click a thumbnail, and the creation comes back as an IMAGE, a VIDEO or an AUDIO socket depending on what it is.
What you set
project and folder are the same pair as everywhere else in the Magnific family - populated after you sign in, narrowed as you choose. project only shows one entry if you're not authenticated, and it says so.
content_type is the filter that decides which output gets populated: image, video or audio. Set it to image and you browse images; only the image output carries the result, and the other two stay empty. That's the tooltip's own note and it explains the most common confusion with this node - people wire the video socket, leave content_type on image, and wonder why it's blank.
selected is set by clicking a thumbnail in the grid, not typed. Leave it alone.
Outputs
image, video, audio (media, whichever matches content_type), creation_identifier and metadata. The identifier is Magnific's handle for the creation, useful if you later want to reference the exact same one again. metadata is the JSON blob - wire it into Magnific Metadata (unpack) if you want the model, prompt, seed or the link to the creation as separate sockets.
Install
cd ComfyUI/custom_nodes
git clone https://github.com/Code2Collapse/ComfyUI-CustomNodePacks.git
Or search "CustomNodePacks" in ComfyUI Manager and restart. The Magnific nodes come with the pack - they're a port of Magnific's vendor pack, magnific-comfyui 0.7.0, and they mount their own magnific.js frontend for the thumbnail grid and sign-in panel. After updating the pack, a hard browser refresh is worth doing if the grid renders oddly, since a 404 in one front-end module can take the pack's whole UI down with it.
Sign in through the Magnific menu or the Magnific Save To node if the project list is empty; credentials go to ~/.magnific/comfyui_auth.json, never into the workflow.
When it's the right node
Mostly it's a bridge between the browser and the graph: things you made in the Magnific web app become assets your local pipeline can consume. It's also the cleanest way to do an iteration loop - generate in Magnific, pull the pick back in, mask it with this pack's local tools, send it out again for another Magnific pass.
Two expectations to set before you lean on it. The grid is drawing from your account over the network, so it's a dropdown you refresh rather than a folder you browse; press R after creating something new. And picking a creation is not a generation - it costs nothing per pick, which is exactly why the other Magnific nodes in this pack deserve a look at your plan before you chain five of them together. Every call on the generation side is metered against your Magnific subscription, and your media is going to their servers rather than staying on your disk. That's the trade the whole family makes.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| project | COMBO | 1 options: β sign in (Magnific menu) and press R to refresh β | |
| folder | COMBO | (project root) | Folder inside the selected project; the list narrows to that project. |
| content_type | COMBO | image | Media type to browse; only the matching output is populated. |
| selected | STRING | Set by clicking a thumbnail in the grid. |
Outputs (5)
| Name | Type | Description |
|---|---|---|
| image | IMAGE | β |
| video | VIDEO | β |
| audio | AUDIO | β |
| creation_identifier | STRING | β |
| metadata | STRING | β |