FromIPAdapterPipe (Inspire)

This is a plumbing node, and it's fine that it's boring. If you've bundled your IP-Adapter setup into an IPADAPTER_PIPE - usually with IPAdapter Model Helper (Inspire) or its ToIPAdapterPipe counterpart - this node opens the bundle back up and hands you the individual pieces. That's the whole job. Pipes exist to keep a graph from turning into spaghetti; the moment you need one of the wires inside the pipe, you use this to get it out.

The pattern shows up all over ltdrdata's packs: bundle a bunch of related things into one fat connection so you can route it around cleanly, then unpack it where you actually need the parts. Impact Pack does the same with BASIC_PIPE. It's a readability tool, not a functional one - nothing about your generation changes, you're just reshaping how the graph is wired.

How it works

An IPADAPTER_PIPE carries the four things IP-Adapter application needs, wrapped in a single connection. FromIPAdapterPipe splits that connection into its members. If you built the pipe with the Model Helper, this is how you reach into it to feed, say, a node that wants a bare IPADAPTER or CLIP_VISION input rather than a pipe. No settings, no processing - it's a demultiplexer.

The inputs and outputs that matter

One input, four outputs, nothing to configure.

• ipadapter_pipe (input) - the bundled pipe. Comes from IPAdapter Model Helper (Inspire) or ToIPAdapterPipe (Inspire).

Outputs are the unpacked contents:

• ipadapter - the IP-Adapter model itself.
• model - the base model (patched, if the pipe came from a FaceID preset carrying a LoRA).
• clip_vision - the CLIP Vision encoder that turns your reference image into embeddings.
• insight_face - the InsightFace model, populated only when the pipe was built for a FaceID preset. On a non-FaceID pipe this one is empty, which is expected.

Wire whichever outputs you need into their destinations and leave the rest unconnected.

How to install it

ComfyUI Manager: search ComfyUI Inspire Pack, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/ltdrdata/ComfyUI-Inspire-Pack

then restart. Dr.Lt.Data's pack, same author as ComfyUI-Manager and the Impact Pack.

Common issues & troubleshooting

insight_face output is empty and something downstream complains. That's not a bug - the InsightFace slot only carries a model if the pipe was built from a FaceID preset. If your downstream node needs InsightFace, go back and make sure the Model Helper preset you chose is a FaceID one. If it doesn't need InsightFace, just leave that output disconnected.

Type mismatch when you connect the pipe. The input strictly wants an IPADAPTER_PIPE. If you're trying to feed it a plain IPADAPTER or a model, that's the wrong node - you don't need to unpack something that isn't a pipe.

Nothing changes in the output image. Right, and expected. This node reorganizes wiring; it has zero effect on the generation. If your IP-Adapter isn't influencing the result, the problem is upstream (wrong preset, weight too low, reference not connected), not here.

The pipe is red / "IPAdapterPlus is not installed." The whole IP-Adapter chain, this node included, sits on top of cubiq's ComfyUI_IPAdapter_plus. Install it through Manager and restart.