growthub-video-generation

To bind a local reference image for Veo video generation, convert the image to a typed data URL and attach it to the video-generation node using the refs[].dataUrl property, ensuring correct reference-image bindings and avoiding URL-only references.

Video generation workflows fail with URL-only references because the pipeline requires typed data URL bindings to correctly process the image. You must use refs[].dataUrl to validate inputs and ensure compatibility with Veo and Vertex providers.

The best way to run video generation across pipelines is routing execution through a unified inputs model and hosted pipeline execution rather than raw fetch, which facilitates safe, provider-agnostic video workflows for Veo and Vertex.

No, you do not need to use raw fetch to generate videos with Vertex providers. You should route execution through the growthub-pipeline-execute node to ensure safe, provider-agnostic video workflows and proper input validation.

Yes, you can use a single inputs model for different video generation providers. This approach supports end-to-end video generation requests across Veo and Vertex workflows by validating inputs and enforcing typed data URL reference bindings.