Google Veo3.1 Fast Text To Video Fast (Channel Edition)
Google Veo 3.1 Fast, text-to-video, as a no-fuss cloud node
- api_config
- video
- request_id
- urls
Google's Veo 3.1, the Fast tier, turned into a three-input text-to-video node: prompt, resolution, aspect ratio. That's the entire Channel Edition surface, and it's honestly refreshing after the way video generation usually works in ComfyUI. No checkpoint, no VAE, no scheduler, no VRAM anxiety. You type, you wait, you get a clip.
Veo 3.1 is Google's flagship video line and, per the community's own running debate, the closed model that open-source efforts like Wan are still chasing - in particular its native audio generation, which has no open equivalent. The "Fast" tier is the speed-focused variant: quicker turnaround and presumably cheaper than the Pro tier, at some cost to top-end quality. For iteration and rough cuts, that's often the right trade.
Why you'd reach for it
Because sometimes you need a moving image now and the local route means a night of setup. The Channel Edition sits on the "fast and simple" end of the Veo 3.1 family: no seed, no negative prompt, no duration control, no audio toggle - just prompt, resolution (720p by default), and aspect_ratio (16:9). If those three are all you wanted, congratulations, this is the node. It's a deliberately skinny wrapper around a hosted API, and the lack of knobs is a feature for people who just want Veo-quality video without learning video-adjacent settings.
How it works
The mechanism is pure cloud call. The node packages your prompt, submits it through BizyAir's channel to Veo 3.1 Fast, polls until the render finishes, and hands back three outputs: video (VIDEO - wire to a Save Video or preview node), request_id (STRING - trace ID), and urls (STRING - where the clip lives). The prompt field is a multiline string, so treat it like a proper video brief: subject, action, environment, camera movement, and audio cues - Veo generates audio natively, and mentioning it pays off.
Two optional inputs keep it workflow-safe: api_config (BIZYAIR_OPENAPI_CONFIG) overrides base_url and api_key for a single request, and skip_error makes a failed call emit an error placeholder instead of aborting the whole queue.
Install and setup
Same one-time install as every node in this pack:
cd ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAirPlus.git
cd BizyAirPlus
python -m pip install -r requirements.txt
Restart ComfyUI (or install "BizyAirPlus" via ComfyUI Manager). No model downloads - the bizyair-cloudberry and bizytrd pip packages auto-install on startup and register the nodes. Then click the BizyAirPlus button in the action bar to ON, create an account at bizyair.ai, enter the API key when prompted (or in Settings > BizyAirPlus > API Key), and queue.
Common issues
- Clip never arrives - switch off or invalid key is the usual story; the ComfyUI console carries the real error.
- Output looks generic - this is a text-to-video model; the prompt is doing all the work. Be specific about camera movement and sound.
- Cost accumulation - every queue is a billed generation. The
skip_errortoggle prevents one failure from nuking the workflow, but the real budget lever is only queueing when the prompt is actually ready.
And the pack caveat, stated once for all these nodes: BizyAir auto-installs and sends your prompts to the cloud, which makes some people uneasy given ComfyUI's history with sketchy custom nodes. It's a legitimate SiliconFlow product, but keep the switch OFF for local-only sessions.
Inputs (5)
| Name | Type | Default | Description |
|---|---|---|---|
| prompt | STRING | Video cue words | |
| resolution | COMBO | 720p | Video resolution |
| aspect_ratio | COMBO | 16:9 | Picture scale |
| api_configopt | BIZYAIR_OPENAPI_CONFIG | 单次请求覆盖base_url和api_key | |
| skip_erroropt | BOOLEAN | false | 开启后遇到错误不中断工作流,输出对应类型的错误占位符 |
Outputs (3)
| Name | Type | Description |
|---|---|---|
| video | VIDEO | — |
| request_id | STRING | — |
| urls | STRING | — |