RH Seedance2.0素材ID/合并

Some nodes deserve a paragraph. This one deserves a sentence and a half. DapaoRHSeedanceAssetIdsMergeNode ("RH Seedance2.0素材ID/合并") takes up to ten asset ID strings - the ones your RH Seedance2.0素材/创建 node produced - and joins them into a single string for the Seedance mini node's asset_ids input. That's it. No API calls, no key required, no network, nothing clever. It's pure plumbing, and every character-consistency workflow that uses the pack's RunningHub Seedance flow passes through it.

What you'll see on it

The schema is about as uncomplicated as ComfyUI gets:

• asset_id1 (required) - the first ID.
• asset_id2 … asset_id10 (optional) - nine more if you have them.

One output: asset_ids, a comma/newline-delimited string. Wire that into the asset_ids input of RH seedance2.0-Mini, and the video node splits it back apart and converts each entry to an asset:// reference so Seedance uses your uploaded character material directly. The mini node's tooltip confirms the format - comma or newline separated - so this merge node is really just making sure you don't hand-assemble that string by hand and typo it.

Install and where it sits

Standard pack install - ComfyUI Manager → search dapaoAPI, or:

cd ComfyUI/custom_nodes/
git clone https://github.com/paolaoshi/ComfyUI-dapaoAPI.git
cd ComfyUI-dapaoAPI
pip install -r requirements.txt

Restart, and the whole asset pipeline looks like this:

Load Image → RH Seedance2.0素材/创建 (asset_id) ─┐
Load Image → RH Seedance2.0素材/创建 (asset_id) ─┼→ RH Seedance2.0素材ID/合并 → RH seedance2.0-Mini
Load Video → RH Seedance2.0素材/创建 (asset_id) ─┘              (asset_ids)

Two practical notes. First, the merge node is optional in a strict sense - you could paste IDs straight into the mini node's asset_ids text field, since it accepts the same format. The node exists to keep that string machine-assembled so you're not copy-pasting IDs between nodes mid-workflow. Second, there's no validation here: if you wire in an empty or stale ID, you'll find out at generation time, not here. If you want a sanity check on whether assets are actually ready, put the 素材/查询 node in the chain instead of trusting the merge. Boring, reliable, and exactly what a workflow in a hurry needs.