Generate and publish daily AI videos to YouTube Shorts with VEO3

See What's Earning in AI Automation Freelancing.
DigiNo helps new AI automation freelancers earn faster by tracking what clients actually pay for.

Most clients who want a YouTube Shorts channel have no idea how to produce daily video content without hiring editors or on-screen talent. This workflow removes both problems by generating, captioning, and publishing cinematic AI videos automatically on a set schedule.

What This Automation Does

Uses Google Gemini to write a niche-specific video prompt, YouTube title, description, and caption with hashtags from a single system prompt you configure once
Sends that prompt to VEO3 to render a vertical 9:16 cinematic video optimised for short-form platforms
Uploads the finished video directly to YouTube Shorts with all metadata pre-filled, no manual intervention required
Sends a Telegram notification confirming each successful publish so the client has visibility without needing dashboard access

Tools Used

n8n
Google Gemini
YouTube
Telegram

Where to Get Hired for This Skill

On Contra, top freelancers across this stack have earned 210 combined verified reviews from real client projects.

Source: Contra freelancer search · refreshed 30 May 2026

Start Earning as a Freelancer on Contra

Contra is a commission-free professional network for independents. Browse live AI automation work and keep what you earn.

Join Contra Free →

How To Build It

Define the niche prompt template

Write a system prompt that locks the AI into a specific content niche (surreal visuals, travel facts, food illusions, etc.) so every video idea generated is consistent with the channel's identity and audience expectations.

Configure the video generation schedule

Set the trigger frequency to match the client's publishing cadence, whether once or twice daily, so the entire pipeline runs and completes without any manual initiation.

Wire Gemini to produce structured output

Connect Google Gemini with a structured output parser so every run returns a discrete video prompt, social caption, YouTube title, and description as separate fields ready for downstream use.

Route the prompt through VEO3 and handle the wait

Send the generated video prompt to the VEO3 API endpoint and build in a polling wait so the workflow holds until the rendered video file is returned before attempting to upload.

Publish to YouTube and confirm via Telegram

Push the completed video file and all Gemini-generated metadata to the YouTube Shorts endpoint, then fire a Telegram message to the client confirming the upload so they have a live audit trail of every post.

Pitfalls

VEO3 render times are variable and can exceed the default wait window, causing the upload step to fire before the video file is ready and returning a failed publish with no alert unless you build explicit error handling into the wait loop.
YouTube OAuth tokens expire and are not automatically refreshed in all environments, meaning the workflow silently fails to upload until the token is manually reauthorised, which clients will blame on the automation rather than the credential expiry.
A single Gemini system prompt governs every video idea the channel ever produces, so if the niche framing is too broad or too narrow the output drifts in tone over time and the channel loses the algorithmic consistency that YouTube rewards.

FAQ

Can I build this without coding?

Yes. The workflow relies on API calls and structured prompts rather than custom code. The only configuration that requires careful attention is the Gemini system prompt, which is plain text you write and refine in a text field.

How long does it take?

A focused build with credentials already set up takes roughly three to five hours. Budget additional time for prompt refinement across a few test runs to make sure the video ideas and metadata stay on-niche.

What can I charge?

Pricing is yours to set based on your market and positioning. Common approaches include a one-time setup fee for handing over a configured workflow, a monthly retainer covering maintenance and prompt updates, or a hybrid of both.

Which tool is required vs optional?

Google Gemini and YouTube are required since they handle content generation and publishing respectively. Telegram is optional but strongly recommended as a client-facing confirmation layer that reduces support questions. VEO3 access via the KIE AI endpoint is required for the video generation step.

This is original DigiNo analysis. The underlying automation pattern is a community workflow template – view the original on n8n.