Embeddr Extract Artifact Info (V2)

When you load an artifact with Embeddr's Load Artifact node, you get back an artifact_info object - and for most people that's where the story ends, because it's a dictionary you can't poke at from the graph. Extract Artifact Info is the tool that pries it open. It takes that EMBEDDR_ARTIFACT_INFO object and pulls out the three things you're most likely to actually want.

It's a pure metadata-plumbing node in the classic ComfyUI sense: no pixels touched, no network call made, nothing generated. Its whole job is converting something opaque into something a downstream node can consume. If you're building lineage-aware workflows - say, uploading a new generation with its parents tagged - this is the node that hands you the parent IDs to feed into the upload.

The three outputs

• parent_ids - the artifact's parent IDs, extracted from the relations/metadata of the artifact info. This is the lineage gold. Feed it straight into Upload Artifact's parent_ids input and your new image automatically records what it was made from.
• tags - a comma-separated string of the artifact's tags. Useful for routing or for building search queries, though you'll often find yourself splitting it with a Text Split-style node first.
• all_json - the full JSON dump of the artifact metadata as a string. This is the escape hatch: when a field you need isn't one of the first two outputs, dump everything and let a JSON-parsing node (or a script) fish it out.

The only input is artifact_info, straight from Load Artifact's artifact_info output. Wire it, done.

Realistic expectations

The source digs for parents in a few places - top-level keys, metadata_json, a comfy_meta subkey - and dedupes them, because the Embeddr API's relation structure varies by version. So parent_ids is best-effort: it'll usually be right, and when it isn't, all_json is right there so you can see what the API actually returned.

Installation is the pack's shared story: get embeddr-cli running (embeddr serve), install embeddr-comfyui via ComfyUI Manager or by extracting a release into custom_nodes, restart ComfyUI. It only needs requests beyond what ComfyUI already has. There isn't much to troubleshoot here precisely because the node does so little - the one real failure is feeding it a stale or empty info object, which yields empty outputs rather than an error. If you're getting nothing back, check what Load Artifact actually returned rather than blaming this node.