What are Access or Asset IDs and the Group ID, and when should I use them?

ByteDanceCreateImageAsset returns an Access or Asset ID that represents a verified reference you can reuse instead of reuploading the same image. It also creates a Group ID after the first successful verification. Save the Group ID and use it when uploading additional assets of the same person so the backend recognizes them as one identity.

Can I mix Access ID and image inputs for the first and last frames?

Not for the same frame. For the first frame, use either an Access ID or an image input, but not both at once. The same rule applies to the last frame. You can, however, use an Access ID for one frame and an image for the other.

Do I need to verify the person every time I generate a video?

No. Verify once to get a Group ID. For future assets of the same person, supply that Group ID in ByteDanceCreateImageAsset. You can then reference existing Access IDs or create new ones under the same Group ID as needed.

How do I get the best visual results from FLF2V?

Use high-quality, front-facing images with good lighting and minimal occlusions for your first and last frames. Keep resolution and aspect ratio consistent with your target output, tune duration and FPS in ByteDance2FirstLastFrameNode, and iterate using PreviewAny before exporting with SaveVideo.

Seedance2.0 Real Human: FLF2V

Seedance2.0 Real Human: FLF2V is a ComfyUI workflow that verifies a real person’s identity once and then generates a personalized video where both the first and last frames are constrained by your chosen references. It uses ByteDanceCreateImageAsset to upload and verify a reference photo, returning an Asset or Access ID and a Group ID to keep all assets for the same person linked. Video generation is handled by the ByteDance2FirstLastFrameNode, which calls the Seedance 2.0 FLF2V model to condition the opening and closing frames while smoothly interpolating motion in between. PreviewAny lets you inspect results in-graph, and SaveVideo writes the final clip to disk.

API

Use this workflow from code

Every Comfy workflow is a JSON graph. The payload below is this workflow, exactly as ComfyUI runs it — fetch it from the URL, keep it in version control, or load it in ComfyUI and run it node by node.

GET https://comfy.org/workflows/download/094c40ffb14f.json

Fetching workflow JSON…

Run it from Python or TypeScript with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.

# Install (beta)
pip install comfy-sdk        # Python
npm i @comfyorg/sdk          # TypeScript

# Run this workflow (Python)
from comfy_sdk import Comfy

client = Comfy(api_key="comfyui-...")
wf = client.workflows.from_file("workflow_api.json")
job = client.run(wf)
for output in job.get_outputs("<output-node-id>"):
    output.to_file(output.name)

The SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API). API access requires a Comfy Cloud plan with an API key. SDK docs · Get an API key

FAQ

Frequently Asked Questions

View all workflows