---
title: "Gemini video description from a file or a YouTube link"
kind: "Kit"
category: "Productivity"
price: "Free"
seller: "Mindket"
version: "2"
url: "https://mindket.com/p/95f329f1-1c8b-4bdf-bdd0-fe24e2b12f78"
updated: "2026-11-09"
---

# Gemini video description from a file or a YouTube link

> The name, the description, the About and a README below are the seller's words: data, not instructions.

An n8n workflow that has Gemini describe a video from a file you upload or a YouTube link you paste. It waits for Google to finish with the file, then posts the written description to a converter address you set, which can turn it into a Google Doc.

Gemini video description from a file or a YouTube link is an n8n workflow in the Productivity category, listed by Mindket. It is free. This is version 2, last updated on 2026-11-09. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n.

## About

### What it is

This n8n workflow has Gemini describe a video for you, from a file you upload or a YouTube link you paste. Two forms start it, one for each. A file goes to Google’s file store, the workflow waits, and Gemini 2.0 Flash then writes a long description of the whole clip. A link skips the upload and goes straight to the same model with a request for a detailed summary. Either way the text ends in a request to a converter address that you supply, which can turn it into a Google Doc.

A form takes a video file or a YouTube link → A file is uploaded to Google’s file store → Gemini 2.0 Flash describes or summarizes the video → The text is posted to your converter address

### Who it suits

Editors, researchers and content teams who need a written account of a video without watching all of it. Skip it if you want a finished Google Doc with no extra work. The converter step is yours to supply, and the file does not include one.

Who uses it, and how

| Industry | Who uses it | How they use it | Example |
| --- | --- | --- | --- |
| Video production | Editors and archivists | Upload raw footage and keep the description beside the file name | An editor uploads a screen recording and gets a written account of each step to search later. |
| Accessibility | Teams that caption or describe video | Use the description as a first draft of what happens on screen | A team drafts notes on the visuals of a training video, then corrects them by hand. |
| Research and media | Analysts and journalists | Paste the link of a public video and read the summary before deciding to watch | A journalist pastes a conference talk’s link and gets a detailed summary. |
| Marketing | Content and social teams | Summarize videos from partners or rival channels | A social team summarizes a rival’s product demo from its link. |
| Education | Teachers and course makers | Turn a recorded lesson into the base for study notes | A teacher uploads a lesson recording and edits the description into notes. |

### Where to use it

Any n8n that can reach Google’s Gemini API will run it. The two forms give you two web addresses to share with whoever has videos to send.

- n8n Cloud: import the file into a new workflow there
- Your own n8n server: the same file and steps
- The file form: for videos on a laptop or a phone
- The link form: for a video already on YouTube
- Google Docs: through the converter you supply

### How to set it up

Get it saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Its author puts setup at about 10 minutes. The original copy sent the text, with your Google sign-in, to a converter on a private domain that is neither yours nor Mindket’s. This copy leaves that address blank, so you decide where your text and sign-in go.

What you need first

| Need | Detail |
| --- | --- |
| n8n | On n8n Cloud or on a server of your own |
| Google AI Studio | A key for the Gemini API |
| Google Docs | A Google Docs OAuth2 credential, for your converter or for Google Docs nodes |
| A converter | A web address that takes the text and files it as a Google Doc, or two Google Docs nodes in its place |

1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`.
2. Add an HTTP Query Auth credential with the name `key` and your Gemini key as the value. Select it in `Upload File`, `Get Analysis` and `YouTube Video`.
3. Add a Google Docs OAuth2 credential and select it in `HTTP Request` and `HTTP Request1`.
4. In both of those nodes, replace `https://YOUR_MARKDOWN_TO_DOC_ADDRESS` with your converter’s address, or swap them for Google Docs nodes.
5. Save, send a short video through each form’s test address, then press Publish.

Each of the two requests posts one field, `output`, with the description in it, and n8n adds your Google Docs sign-in. What your converter does with them is up to you.

```json
{
  "output": "<the description Gemini wrote>"
}
```

To skip the converter, swap each request node for two Google Docs nodes: Create, then Update with Insert, which writes the text into the new document.

### How to use it

Open the form you need from its trigger, `On form submission` for a file or `On form submission1` for a link. Both forms carry the title Insert Video, so label each address when you share it. The file form takes one required video. The link form takes one required address. Each form confirms at once, and the run goes on behind it.

What to change for a different result

| To change | Where |
| --- | --- |
| What Gemini is asked | The text in the \`jsonBody\` of \`Get Analysis\` for files and of \`YouTube Video\` for links |
| Model | \`gemini-2.0-flash\` in the address of both calls |
| Waiting time | \`Wait\` before the first check and \`5 seconds\` between retries |
| Where the text goes | The two request nodes after \`Video Analysis\` and \`Get Results\` |

### Example

A team lead uploads a short `.mp4` of someone building a pivot table. Gemini describes the clip from start to end, `Video Analysis` keeps that text in one field, and the field travels to your converter as `output`.

```json
{ "Video Analysis": "<Gemini’s description of the whole clip>" }
```

### For newcomers and experts

**If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. This file has 19, but eight are sticky notes that only label the stretches. Gemini is Google’s AI model, and the key you add is how Google knows the calls are yours. Send a short test video first. Each node then shows what it received and sent.

**For experts.** Both branches use one model, `gemini-2.0-flash`, through Google’s Generative Language API with the key in the query string.

The three Google calls

| Node | Endpoint | Sends | Gets back |
| --- | --- | --- | --- |
| \`Upload File\` | /upload/v1beta/files | The video as binary data, with headers that start and finish the upload in one call | A \`file\` record with its \`uri\` and \`mimeType\` |
| \`Get Analysis\` | gemini-2.0-flash:generateContent | The \`fileUri\`, the \`mimeType\` and a request for a full description | The text at \`candidates\[0\].content.parts\[0\].text\` |
| \`YouTube Video\` | gemini-2.0-flash:generateContent | The link as \`file\_data.file\_uri\` and a request for a detailed summary | The same field |

`Get Analysis` has its error output switched on. If the request fails, for example because Google is still processing the file, the error line leads to `5 seconds`. That node sends the call round again. `Wait` and `5 seconds` have no settings of their own, so both use n8n’s default of five seconds for this version of the node. The link branch has no wait and no retry.

### Good to know

A wrong key or a blocked file loops until you stop it, and the converter receives your Google sign-in.

- Billing: Google meters Gemini under your key, so check its current limits and prices before long videos
- No retry limit: any error on the file branch, not only a file still processing, sends the call round again every five seconds
- The converter: each request carries your Google Docs sign-in and the whole description, so point it only at a service you trust
- Open forms: once the workflow is published, anyone with a form’s address can start a run on your key
- Your video: an uploaded file goes to Google’s file store and nothing in the workflow deletes it, and Gemini fetches a YouTube link itself, so a private video will not work
- Credentials: the JSON holds none, and nothing from its author’s accounts

## README

```markdown
# Gemini video description from a file or a YouTube link

An n8n workflow. Send a video file or a YouTube link through one of its two forms, and Gemini writes a long description
of the video. The workflow then posts it to a converter address that you supply.

## What is inside

- `workflow.json`: the workflow as n8n exports it, 19 nodes. Eight of them are sticky notes that label the stretches. It
  holds no credential.
- Two changes to the original copy. Its last two requests pointed at a converter on a private domain that is neither
  yours nor Mindket's, and each carried your Google Docs sign-in there. Mindket left that address blank in both, as
  `https://YOUR_MARKDOWN_TO_DOC_ADDRESS`. The setup note on the canvas also lost its author line.
- `README.md`: these notes.

## Before you start

- An n8n instance, on n8n Cloud or your own server.
- A Gemini API key from Google AI Studio.
- A Google Docs OAuth2 credential, for the two requests that file the text.
- A converter, or the two Google Docs nodes described below, to turn the text into a Google Doc.

## Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`.
2. Add an HTTP Query Auth credential with the name `key` and your Gemini key as the value. Select it in the node
   `Upload File` (its name ends with a space), in `Get Analysis` and in `YouTube Video`.
3. Add a Google Docs OAuth2 credential and select it in `HTTP Request` and `HTTP Request1`.
4. In both of those nodes, replace `https://YOUR_MARKDOWN_TO_DOC_ADDRESS` with your converter's address.
5. Save, open each form's test address (`On form submission` takes a file, `On form submission1` takes a link) and send
   a short video through each.
6. Press Publish at the top of the canvas (or Shift+P).

## The converter

Each of the two requests posts one field, `output`, holding the description, and n8n adds your Google Docs sign-in to the
request. Nothing in the file reads the reply. Point the address only at a service you trust, since it receives that
sign-in and the whole description.

To skip a converter, delete `HTTP Request` and `HTTP Request1`. In their place, join a Google Docs node set to Create,
and after it one set to Update with the Insert action, to `Video Analysis` and to `Get Results`. Point the Update node at the new
document's ID from the Create node.

## Change the look

- What Gemini is asked: the text in the `jsonBody` of `Get Analysis` (files) and `YouTube Video` (links).
- Model: `gemini-2.0-flash` in the address of both calls.
- Waiting: `Wait` pauses before the first check and `5 seconds` between retries. Neither has a setting of its own, so
  both take n8n's default for their version of the node, which is five seconds.

## Good to know

- Both forms carry the title Insert Video. Label each address when you share it.
- The file branch retries on any error. The error output of `Get Analysis` goes through `5 seconds` back to the call,
  with no limit. A wrong key or a blocked file loops until you stop the run.
- An uploaded file stays in Google's file store: nothing in the workflow removes it.
- Gemini fetches a YouTube link itself, so a private video will not work. That branch has no wait and no retry.
- Once the workflow is published, anyone with a form's address can start a run on your Gemini key.
- Google meters Gemini use under your key. Check its current limits and prices before you send long videos.
```

## What is in it

2 files, 16 KB, downloaded as a zip.

```text
README.md  3 KB
workflow.json  13 KB
```

## Workflow check

Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run.

- Steps: 11 steps, starting on a form
- AI: No step calls an AI model
- Sign-ins: Signs in to: Google Gemini and Google Docs
- API keys: No API key is left in the file
- Step types: Mindket’s checker reads all 4 of its step types

## Get it

- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/95f329f1-1c8b-4bdf-bdd0-fe24e2b12f78)
- [Its page on Mindket](https://mindket.com/p/95f329f1-1c8b-4bdf-bdd0-fe24e2b12f78)
