Wan Bailian CN T2I Config

Wan 2.7 has no weights. Alibaba stopped open-weighting the numbered Wan line after 2.2, so everything from 2.5 on is API-only, and any page promising you a local Wan 2.7 download is lying to you. That's the entire reason this node exists: it's the legitimate front door to Alibaba's closed Wan 2.7 image models from inside ComfyUI. No 27B checkpoint, no VRAM, no model files - just an API key.

It ships in ComfyUI MediaHub (vantang), a pack that wraps a handful of cloud media APIs - MiniMax, Agnes, Seed Volcengine, and this one, Alibaba Cloud's Bailian/DashScope platform. The Wan Bailian CN T2I Config node is a config node: it doesn't call anything by itself. It builds a request and hands it off to the pack's generic execution node.

How it fits in the workflow

Prompt text -> WanBailianCNT2IConfig -> MediaHub Generate Image -> Preview Image
API Key -------------------------------------------> MediaHub Generate Image

The config node's only output is a request (typed MEDIAHUB_IMAGE_REQUEST). You feed that, plus an API key, into MediaHub Generate Image, which does the actual HTTP work and returns a normal ComfyUI IMAGE tensor, plus image_urls and raw_json for debugging. That provider-config / neutral-execution split is the pack's whole design: config nodes stay provider-specific, execution nodes stay generic and key-aware.

Under the hood it's a synchronous POST to DashScope's multimodal-generation/generation endpoint, authenticated with a DASHSCOPE_API_KEY bearer token. MediaHub then downloads the returned image URL and converts it into a tensor - so your ComfyUI box needs outbound network access to Alibaba's storage, not just to the API.

The inputs that matter

• model - wan2.7-image-pro or the cheaper wan2.7-image. Pro is the 4K-capable one; the base caps at 2K.
• size - 1K, 2K, or 4K. The node shows all three regardless of model, but pick 4K on the non-pro model and the API rejects the request - the node won't stop you.
• n - how many images per run, 1 to 4. More images means more billable generations, so don't leave this cranked for throwaway tests.
• seed - -1 (the default) means random and isn't sent at all. Set a positive value for reproducible runs.
• watermark - off by default; flip it on if you need provenance.
• prompt - forceInput, so wire it from a Primitive String node or whatever text source you already use.

Installing it

The pack's registry id is mediahub-cloud, so in ComfyUI Manager search for "MediaHub". If it hasn't shown up in Manager's list yet (the registration was still landing at first release), the manual route is the same as every custom node:

cd ComfyUI/custom_nodes
git clone https://github.com/vantang/ComfyUI-MediaHub.git
/path/to/ComfyUI/python -m pip install -r ComfyUI-MediaHub/requirements.txt
# restart ComfyUI

Good news: the dependencies are just requests, Pillow, and numpy. No torch wheels, no model downloads, nothing heavy. The real prerequisite is a DASHSCOPE_API_KEY from Alibaba's Bailian console.

Where people get burned

• Regional access. These models live on the China console (bailian.console.aliyun.com, Beijing endpoint), and international Alibaba Cloud accounts don't carry them. Getting a valid key can mean mainland-China account verification - a genuine pain point if you're outside the region, and the most common cause of a key/auth failure before you ever see an image.
• The key widget masks but doesn't protect. MediaHub's key field is password-masked on screen, but the value can still land in exported workflow JSON and generated-media metadata. The README says it straight: strip the key before sharing, and rotate if you suspect it leaked.
• It re-runs every queue. MediaHub Generate Image is marked always-changed, so it fires on every execution regardless of caching. Fine for interactive use; a silent billing leak if you leave a graph auto-queued.
• It's synchronous. The DashScope image call blocks with a 180-second HTTP timeout, so a slow multi-image 4K job can time out at the wire level even though the API would finish.

If you have DashScope access and want closed Wan 2.7 images without the giant GPU, this is the cleanest path into ComfyUI around. The pack is young, so treat the API contract as still settling - but the plumbing is solid.