Skip to content

Every 15 minutes

Publish rendered videos from Drive to YouTube

Videos your editing or AI video tool saves to Drive are uploaded to YouTube with a title and description, then moved to a Published folder.

Runs
Every 15 minutes
Apps
Google Drive, YouTube
AI
Yes, uses the built-in AI allowance
Access
Drive read+write; YouTube youtube.upload

Send this to your assistant

Create a ClickRuntime automation: every 15 minutes, check my Renders folder in Drive. For each new video, write a title and description with AI from the file name and any matching script file, upload it to YouTube and move the file to my Published folder.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A content team makes videos with an AI video tool that saves each render to Google Drive. The renders come out at all hours, and someone has to collect them, write metadata and upload them. Files pile up and it is hard to tell which have been published.

Publishing straight from the Renders folder and moving each file afterwards keeps the channel up to date and makes the folder itself show what is still waiting.

What you get out of it

  • Renders go live without waiting

    A finished render is on YouTube within a quarter of an hour.

  • The folder shows what is left

    Published files move out of the Renders folder, so what remains is the real backlog.

  • Metadata written for you

    AI writes the title and description from the file name or the script saved next to it.

  • Works with any tool that saves to Drive

    Editing software, AI video tools and freelancers can all drop files in the same folder.

How it works

What happens, step by step

  1. Every 15 minutes, ClickRuntime checks your Renders folder in Google Drive for video files.

  2. AI writes a title and description for each one from its file name.

  3. The video is uploaded to your YouTube channel.

  4. The file is moved to your Published folder, so it is never uploaded twice, and you get an email with the link.

Before it runs live

  • Connect Google Drive
  • Connect YouTube

What you get

RunsEvery 15 minutes
Publish rendered videos from Drive to YouTubetoday, 9:00Succeeded
Email · PublishedPublished: 5 warehouse layouts that cut picking time, https://youtu.be/Rt5Yu6Io7Pa

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Act only on the items that match your own rules, and skip the rest
  • Change what the AI looks for, or how it writes the result
  • Add another app, for example also send it to Slack
  • Combine it with other Google Drive and YouTube steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
publish_rendered_videos_from_drive_to_youtube.pyexample
import io
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from googleapiclient.http import MediaIoBaseUpload
from clickruntime import on_trigger, report_fetched, credentials, ai, notify

def api(name, version):
    return build(name, version, credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False)

RENDERS, PUBLISHED = "renders-folder-id", "published-folder-id"

@on_trigger
def run(event):
    drive = api("drive", "v3").files()
    files = drive.list(q=f"'{RENDERS}' in parents and mimeType contains 'video/' and trashed=false", fields="files(id,name)").execute()["files"]
    report_fetched(len(files))
    if not files:
        return {"summary": "No new renders"}
    for f in files:
        meta = ai.generate(f"File: {f['name']}", system="Write a YouTube title (max 90 chars), a 3-sentence description and 8 tags.",
                           json_schema={"type": "object", "properties": {"title": {"type": "string"}, "description": {"type": "string"}, "tags": {"type": "array", "items": {"type": "string"}}}}, max_output_tokens=300).json
        media = MediaIoBaseUpload(io.BytesIO(drive.get_media(fileId=f["id"]).execute()), mimetype="video/mp4", resumable=True)
        video = api("youtube", "v3").videos().insert(part="snippet,status", media_body=media,
                body={"snippet": meta, "status": {"privacyStatus": "public"}}).execute()
        drive.update(fileId=f["id"], addParents=PUBLISHED, removeParents=RENDERS).execute()
        notify.email_me(f"Published: {meta['title']}", f"https://youtu.be/{video['id']}")
    return {"published": len(files)}

FAQ

Common questions

Can it use the script to write the description?
Yes. If a text or doc file with the same name sits next to the video, its contents are used to write a better description.
What happens if an upload fails?
The file stays in the Renders folder and you get an email with the reason, so it is retried on the next run.
Can I choose the privacy setting?
Yes. Public, unlisted or private, set once in the prompt.
What permissions does it need?
Drive read+write; YouTube youtube.upload. Nothing else in your accounts is used.
Does it need AI?
Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.
How many runs does it use?
One run each time it checks. Checks that find nothing new and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Publish rendered videos from Drive to YouTube” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.