☁️BizyAir PassParameter

Let's be straight about this one: the node's own metadata lists no required inputs, no optional inputs, and no outputs at all. That's unusual enough to be worth flagging rather than papering over - most nodes in this pack, even the simplest loaders, declare at least one typed socket. PassParameter declares none.

What that almost certainly means in practice is that this is a dynamic-typed utility node - the sockets get created or typed at runtime based on what you wire into or out of it, the way a Reroute node in stock ComfyUI works, rather than having a fixed shape declared up front. Reading the name literally, "pass parameter" suggests exactly that kind of job: relaying a value from one point in a graph to another, possibly across a subgraph or group boundary, without ComfyUI's schema system needing to know in advance what type that value is. That's a reasonable guess based on the name and the empty schema, but it is a guess - the honest answer is that the static information available doesn't describe this node's actual behavior, and the only way to know for certain is to drop it into the editor and see what sockets it offers once it's on the canvas.

Given that, this article is going to stay short and refuse to invent parameters, tooltips, or a worked example that the source data doesn't support. That's a deliberate choice, not laziness - making up plausible-sounding inputs for a node like this would be actively worse than admitting the gap.

Installing it

The pack-level instructions still apply even though this specific node's behavior is unclear. Through ComfyUI Manager: search BizyAir, click Install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAir.git

Restart ComfyUI, and set your BizyAir API key on first use - the README is explicit that this step is required before any BizyAir node actually executes, though a node this minimal may not even need cloud credentials to function, since it doesn't obviously produce cloud-generated content.

What to actually do if you're stuck on this node

Two practical options, in order of usefulness. First, drop it on the canvas and look at it directly - ComfyUI will show you whatever sockets it actually exposes once instantiated, which is more reliable than anything a static schema dump can tell you. Second, if you found this node inside someone else's shared workflow rather than adding it yourself, look at what's connected to it in that workflow - the neighboring nodes and their types will tell you far more about its real job than the node's own declared schema does, since a pass-through utility's behavior is defined by what's plugged into it, not by anything intrinsic to the node.

If you figure out exactly what it does, that's genuinely useful information this article doesn't have - the gap here is real, not a formality.