Automate Google Drive + YouTube
Where the documents live — and pile up. Long-form content worth repurposing everywhere else. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Content Producer already works across Google Drive and YouTube — free, and it runs on your machine.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from Google Drive into YouTube.
When a file lands in a folder in Google Drive…
…an agent can pull transcripts and stats in YouTube — after reading the context and deciding it should.
When a doc is updated in Google Drive…
…an agent can draft descriptions and chapters in YouTube — after reading the context and deciding it should.
When a file is shared in Google Drive…
…an agent can summarise comments in YouTube — after reading the context and deciding it should.
When a video is published in YouTube…
…an agent can read and summarise documents in Google Drive — with the reasoning recorded in the run’s receipt.
When a comment arrives in YouTube…
…an agent can file outputs into folders in Google Drive — with the reasoning recorded in the run’s receipt.
Google Drive to YouTube, setup template
Start with the google-drive-api node and the youtube-api node. Configure the Google Drive source payload, the agent input, and the YouTube operation. The sequential template does not implement conditional writes or approval by itself.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "b5b2fea8-d885-42ae-a3d6-bae87a65e044",
"name": "Google Drive → YouTube",
"nodes": [
{
"id": "c8ac712e-13e8-415d-a1ab-d4af9cafc076",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "66f45fcd-402b-4ee9-afb3-964e210e45ea",
"text": "Read Google Drive",
"x": 512,
"y": 336,
"isEditing": false,
"type": "google-drive-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "LIST_FILES",
"folderId": "CONFIGURE_FOLDERID"
},
"description": "Setup template for Google Drive API. Interact with Google Drive to perform various operations on files and folders. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "aa4bcc35-04de-47e9-aba8-cb3c8fb538e6",
"text": "Review source and draft",
"x": 512,
"y": 528,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Google Drive item. Decide whether it warrants action in YouTube, and explain why.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "349bc3f1-ae64-46fa-a28b-bd29fcda5260",
"text": "Configure destination in YouTube",
"x": 512,
"y": 720,
"isEditing": false,
"type": "youtube-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "ADD_VIDEO_TO_PLAYLIST",
"playlistId": "CONFIGURE_PLAYLISTID"
},
"description": "Setup template for YouTube API. Interact with the YouTube API to manage videos, comments, playlists, and more. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "bba457f8-cb02-4cd0-a7b2-2b4297de1e68",
"start": {
"id": "c8ac712e-13e8-415d-a1ab-d4af9cafc076",
"type": "output"
},
"end": {
"id": "66f45fcd-402b-4ee9-afb3-964e210e45ea",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "2c5b1b10-b5be-48a3-a55a-1471f8351982",
"start": {
"id": "66f45fcd-402b-4ee9-afb3-964e210e45ea",
"type": "output"
},
"end": {
"id": "aa4bcc35-04de-47e9-aba8-cb3c8fb538e6",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "9991ea08-9b6a-485c-a5e5-9058237c6a6c",
"start": {
"id": "aa4bcc35-04de-47e9-aba8-cb3c8fb538e6",
"type": "output"
},
"end": {
"id": "349bc3f1-ae64-46fa-a28b-bd29fcda5260",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Google Drive API
Interact with Google Drive to perform various operations on files and folders.
- action — The action to perform on Google Drive Current example:
LIST_FILES. - folderId — The ID of the folder (for LIST_FILES, UPLOAD_FILE, CREATE_FOLDER) Current example:
CONFIGURE_FOLDERID.
Configure YouTube API
Interact with the YouTube API to manage videos, comments, playlists, and more.
- action — The action to perform on YouTube Current example:
ADD_VIDEO_TO_PLAYLIST. - playlistId — The ID of the playlist Current example:
CONFIGURE_PLAYLISTID.
Install Content Producer
Content Producer already uses both Google Drive and YouTube, so installing it gives you this exact hand-off wired up — connected, editable, and running on your own machine.
Runs on your own machine · See what it does
What building this looks like
- Download AGNT Community Core — free and local-first.
- Connect Google Drive with one OAuth sign-in and YouTube with one OAuth sign-in; both land in the local vault.
- Start from a marketplace workflow, or drop google-drive-api and youtube-api onto the canvas with an agent between them.
- Put an approval gate on anything consequential, then run it — the receipt shows what was read in Google Drive and what was written to YouTube.
Google Drive and YouTube — common questions
Can I connect Google Drive to YouTube without writing code?
No code is required. Add both connections in the vault (Google Drive uses one OAuth sign-in, YouTube uses one OAuth sign-in), then either install a marketplace workflow for this pair or drag the two nodes onto the canvas and put an agent between them.
How is this different from a field-mapping Google Drive to YouTube automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles auto-summarise incoming docs the way a colleague would — reading the Google Drive context, judging it, then writing to YouTube with the reasoning recorded.
Does my Google Drive and YouTube data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to Google Drive, YouTube and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Google Drive and YouTube run leave behind?
Every run is recorded end to end — the Google Drive items examined, the decision and its reasoning, the resulting YouTube write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
