A workflow template published on n8n.io on 14 October 2026 shows how a web form can produce a presenter-style video with little manual editing. The template connects n8n to the useapi.net Google Vids API and its Gemini Omni 1.1 Flash model. A user describes a presenter, picks a voice, pastes a script and sets the format. The workflow then returns a finished MP4 with a preview page and a download link. It is aimed at creators and small teams who want talking-avatar clips without filming a person.
What n8n is and why this template matters
n8n is a workflow automation tool that lets technical and non-technical users connect apps and services through a visual editor. Templates such as this one act as ready-made starting points. Instead of building each step from scratch, a user can import a working sequence and adjust it to their needs. In this case, the template bundles a form, several API calls, status checks and a results page into one flow.
The source describes the template as a complete pipeline rather than a single tool. That distinction matters for readers who want to automate video production. The form handles input, the API handles generation, and the workflow handles everything in between, including review steps and media delivery.
How the workflow turns a form into a video
The process starts with an n8n form, which is opened at a fixed path once the workflow is activated. The user can describe a new presenter or select one saved in their Google Vids account. They also choose a voice, write the script, and set the scene, aspect ratio and length. Optional additional segments can be included in the same submission.
If a new presenter is needed, the workflow submits a request to draw one. A review page then lets the user confirm the portrait and the voice. If the result does not suit the project, the previous avatar can be deleted and a new portrait generated. This step gives users a chance to correct the look before any video is produced.
After approval, the workflow submits a generation job to the useapi.net Google Vids API. It creates a 720p talking-avatar clip and polls the job status until the clip is ready. Users do not need to watch the job manually, which is one of the main practical benefits of wrapping the process in automation.
Extending clips and optional 1080p upscaling
For longer productions, the workflow extends the clip one segment at a time, using additional prompts for each part. After every segment, a checkpoint page lets the user either continue or stop early. This design gives people a point to review progress before more generation takes place.
A 1080p upscale is available, but only when the total duration is 20 seconds or less. Once processing is complete, a results page displays an embedded player and an MP4 download link. The source notes that media is streamed through an n8n webhook that fetches files from useapi.net using a media ID. This arrangement keeps the API token on the server, so it never reaches the browser. Users who no longer want the generated presenter can also choose to delete it.
Costs, requirements and setup
Running the template is not free in practice. The source lists a useapi.net subscription at $15 per month, described as a flat fee covering every useapi.net API. The Google side is also required. The user needs a Google account on a paid Google AI plan, either Pro or Ultra, connected once through the useapi.net Google Vids setup page. Videos and images draw on that account's monthly Google Vids allowance. A free Google account can only be used to create avatars.
The result page includes a cost estimate. It is driven by two rate constants in its code node, which by default assume the Ultra plan at $199 with 10,000 seconds of video a month. Anyone on a different plan needs to edit those constants so the estimate reflects their own allowance. useapi.net states that it adds no per-video charge, which means the real cost depends on the Google plan.
Setup requires a single Header Auth credential in n8n, with the Authorization header set to a Bearer token. The source says the workflow runs on self-hosted or cloud n8n and uses only core nodes. Once the workflow is active, the form is ready for submissions.
Customization options
- Change the default voice, framing, format or length on the first form, or reduce the list of 30 voices to those a brand actually uses.
- Edit the rate constants so the cost estimate matches a specific Google AI plan.
- Send finished MP4 files to Google Drive, S3, Slack or a social media platform by adding a node after the download step.
- Remove the extend section or the upscale option if only short single clips are needed.
Transparency and points to weigh
The template is published by useapi.net, the company behind the API it calls. The source discloses this relationship directly, and readers evaluating the workflow should keep it in mind. Vendor-published templates can be a fast way to start, but users should check the configuration and cost assumptions themselves.
The source also notes that every Vids clip carries Google's visible Gemini mark and an invisible SynthID watermark. For anyone planning to publish avatar footage, that labelling is an important detail. Viewers may see the visible mark, and the watermark is present regardless of how the clip is later shared.
Further resources are linked from the source, including the Google Vids API documentation, a tutorial on AI influencer videos with avatars, and code examples with an agent skill hosted on GitHub.
Outlook for teams using n8n
For teams already working in n8n, the template offers a practical route to presenter-led video without a separate editing suite. The workflow handles review, generation, checkpoints and delivery in one place. Its main limit is the monthly Google Vids allowance behind it. The plan a team chooses, rather than the automation itself, will largely determine how many clips it can produce.
Related: n8n Workflow Parses Gmail Invoices Into Sheets With Slack Alerts · Free Tool Converts OpenAI, Flowise and Pipedream Workflows to n8n
Comments (0)