BizyAirPlus NodeWrapper

Let's get the honest part out of the way first: this node is the boring end of BizyAirPlus, and that's by design. The BizyAirPlus NodeWrapper is an output node - a sink, not a source - that the cloud runtime uses to hand execution status back to your local ComfyUI session. You will almost certainly never add it by hand, and if you're building a workflow from scratch you can ignore it entirely.

What it actually does

BizyAirPlus works by taking the workflow you built locally, shipping it to BizyAir's cloud to run the heavy parts, and returning the results into your local graph. Something has to be the landing pad for that return trip, and this node is it. It's flagged as an output node, which in ComfyUI terms means it sits at the end of a graph as a terminal point - nothing feeds forward out of it.

Its three inputs are all strings:

• input - a JSON blob (default {}). The serialized input the cloud side echoes back.
• prompt_id - ties this wrapper to a specific queued run, so status lands on the right execution.
• extra_data - another JSON blob (default {}) for whatever metadata the runtime needs to round-trip.

And it outputs a single status string. That's it. No image, no model, no settings. If you look at the inputs and think "that's a developer-facing API surface wearing a node costume," you're right.

Why it exists

When you toggle BizyAirPlus ON and queue a workflow, the pack serializes the graph and submits it to BizyAir for execution. The wrapper is part of that handshake - a well-known place where the cloud side can report back status and the prompt_id that identifies the run. It also shows up in workflows you export from BizyAir's own examples, which is the most common way beginners end up staring at it and wondering what they're supposed to wire in.

So the practical advice: if you loaded someone's BizyAir workflow and this node appears, leave it alone. Don't delete it expecting things to speed up, and don't try to "connect" it - it's doing bookkeeping, not processing.

The only two things you need to know

First, this node assumes BizyAirPlus is configured. No API key, no cloud execution, and a wrapper with nothing to report. The key lives in Settings > BizyAirPlus > API Key, or you set BIZYAIR_API_KEY before starting ComfyUI. Second, if the node shows up in a workflow but the pack's action-bar button is OFF, the graph will run locally and the wrapper is effectively a no-op - it won't crash, it just won't do anything useful.

Install

It ships with the rest of the pack, so there's nothing special:

cd /path/to/ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAirPlus.git
cd BizyAirPlus
python -m pip install -r requirements.txt

Then restart ComfyUI. ComfyUI Manager can also grab it if you search "BizyAirPlus."

The wrapper is not a node you'll write articles about - it's a node you'll pretend doesn't exist until a cloud workflow breaks and you realize it was the thing quietly reporting status back. Knowing it's there means you won't waste an hour trying to wire it into your graph.