Automate Google Calendar + YouTube
The shared clock your workflows can read and write. 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.
Meeting Follow-Through is a ready-made agent built around Google Calendar; point its last step at YouTube to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Google Calendar side, works out what it means, and only then decides what — if anything — should happen in YouTube.
When an event starts or ends in Google Calendar…
…an agent can pull transcripts and stats in YouTube — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can draft descriptions and chapters in YouTube — after reading the context and deciding it should.
When a day begins in Google Calendar…
…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 create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a comment arrives in YouTube…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
Copy this Google Calendar → YouTube workflow
Start with the google-calendar-api node and the youtube-api node. Configure the Google Calendar 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": "946fc78a-5875-4ac4-a0f7-771c4ecf2218",
"name": "Google Calendar → YouTube",
"nodes": [
{
"id": "d4968c1e-7d06-4539-a945-534de4d3dac6",
"text": "Watch Google Calendar",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-calendar-new-event",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"calendarId": "CONFIGURE_CALENDARID"
},
"description": "Setup template for Google Calendar New Event. Listen for events created or updated on a Google Calendar and trigger the workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "64ed8380-0c3d-42e4-a609-0fa4ceb1980c",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Google Calendar 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": "b65a93ec-fac4-489f-a5a3-883f2d11d9aa",
"text": "Configure destination in YouTube",
"x": 512,
"y": 528,
"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": "b955cc35-42e7-4e9c-a5bd-60310e8de878",
"start": {
"id": "d4968c1e-7d06-4539-a945-534de4d3dac6",
"type": "output"
},
"end": {
"id": "64ed8380-0c3d-42e4-a609-0fa4ceb1980c",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "268138bc-57b2-429f-a590-ab8d64eb03ce",
"start": {
"id": "64ed8380-0c3d-42e4-a609-0fa4ceb1980c",
"type": "output"
},
"end": {
"id": "b65a93ec-fac4-489f-a5a3-883f2d11d9aa",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Google Calendar New Event
Listen for events created or updated on a Google Calendar and trigger the workflow.
- calendarId — Calendar ID to monitor (defaults to 'primary') Current example:
CONFIGURE_CALENDARID.
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 Meeting Follow-Through
Meeting Follow-Through is a working agent built around Google Calendar. Install it, point its last step at YouTube, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Wiring Google Calendar to YouTube
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise YouTube (one OAuth sign-in) and Google Calendar (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; google-calendar-api does the reading and youtube-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
Google Calendar and YouTube — common questions
Can I connect Google Calendar to YouTube without writing code?
You can build it entirely from the canvas. Authorise Google Calendar with one OAuth sign-in, YouTube with one OAuth sign-in, then tell the agent what prep briefings before every meeting should look like once YouTube is involved. Code is an option for the unusual cases, never a requirement for the common ones.
How is this different from a field-mapping Google Calendar to YouTube automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles prep briefings before every meeting the way a colleague would — reading the Google Calendar context, judging it, then writing to YouTube with the reasoning recorded.
Does my Google Calendar 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 Calendar, YouTube and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Google Calendar and YouTube run leave behind?
You get an auditable trail rather than a success flag. It shows the Google Calendar context the agent worked from, the judgment it made about videos become posts, threads and newsletters, and the exact change applied in YouTube, with approvals attached where you required them.
