EZ Input

EZ Input is the pack's most honest node, in that the author's own description tells you not to use it unless you specifically need what it does. It's a multiline text box that outputs a string - but it tags that output with the ANY type instead of STRING. That's the entire trick, and it exists to solve one annoying ComfyUI situation.

What "ANY" actually buys you

In ComfyUI, some custom widgets are what the author calls "combo" input slots - dropdown-ish fields that expect an incoming wire of a particular type. If a node's widget is typed INT, a plain STRING wire won't plug into it. A node like EZ Switch, which can pass anything through, needs inputs that can accept any type, and a normal text node's STRING output refuses to mate with an * input in some layouts. By lying and declaring its output as ANY, EZ Input plugs into those combo slots where a regular string node won't.

That's genuinely it. The mechanism is trivial - one multiline String input in, one string out - but the type tag is the product. Where people hit it: they're wiring a preset text into a switch or a loader's hidden widget and ComfyUI just won't let the wire snap, and this node is the workaround.

The honest advice

The author says it plainly in the node's own description: if you don't need the ANY output, use the ComfyUI core String (Multiline) node instead and don't install this pack for this node alone. He keeps it around "for testing purposes" - it's a utility for his own workflows. That's a refreshingly self-aware take, and it's the right call: the core node does the same job with a real STRING type and zero surprises.

Install and usage

It comes with the EZ-AF Nodes pack:

cd ComfyUI/custom_nodes
git clone https://github.com/ez-af/ComfyUI-EZ-AF-Nodes.git

restart ComfyUI (or grab it via ComfyUI Manager → search ez-af). No dependencies beyond the pack's own aiohttp/Pillow, no models.

Where it bites

Because the output is ANY, ComfyUI can't type-check what you plug it into, so if you wire it somewhere that expects a number or an image, you'll only find out when the graph errors at queue time. And if you're using this instead of a core string node everywhere out of habit, you're taking on that risk for nothing. It's a scalpel, not a hammer - reach for it when a combo slot won't accept a normal string wire, and use the core node for everything else.