GuidesBuild with VideoGenLibraries & SDKs

n8n

Automate VideoGen from n8n with the community node.

n8n-nodes-videogen is the official n8n community node for VideoGen. It lets you generate images, videos, voiceovers, sound effects, music, and talking-head avatar clips — and run end-to-end video workflows — directly from your n8n automations, with no code.

The node is generated from the VideoGen developer API OpenAPI spec, so it stays in lockstep with the API.

Install

Follow the community nodes installation guide. In n8n, go to Settings → Community Nodes → Install and enter the package name:

n8n-nodes-videogen

Authenticate

The node supports two credential types:

  • OAuth2 (Sign in with VideoGen) — connect your VideoGen account without copying keys.
  • API Key — create one at app.videogen.io/developers and paste it into a VideoGen API credential.

The VideoGen node

Add the VideoGen node to a workflow, pick a Resource, then an Operation. The node exposes every VideoGen API capability grouped by resource:

ResourceWhat it does
WorkflowRun end-to-end video workflows (script to video, voiceover to video, slideshow to video, storyboard to video) and manage runs.
ToolGenerate individual assets — images, video clips, voiceovers, sound effects, music, avatars — and run editing tools.
ProjectList, fetch, export, and remix projects.
FileUpload, fetch, list, search, and manage files.
ResourceDiscover avatar presenters, TTS voices, and supported languages.
TextGenerate scripts and other text.
WebhookManage webhook endpoints.
AccountFetch the current account.

Long-running operations (workflow runs and tool executions) return an id you can poll with the matching get operation, or wait on with the trigger below.

The VideoGen Trigger node

The VideoGen Trigger node starts a workflow when VideoGen sends a subscribed event — for example, when a workflow run or tool execution finishes. Select the events you care about; the node registers a webhook endpoint scoped to those events and removes it when the trigger is disabled.

This lets you build fully event-driven automations: kick off a script-to-video run from one workflow, and have a separate workflow fire the moment the finished video is ready.