Automate Google Calendar + Google Drive
The shared clock your workflows can read and write. Where the documents live — and pile up. 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 Google Drive to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Google Drive is a decision about the Google Calendar event rather than a transcription of it.
When an event starts or ends in Google Calendar…
…an agent can read and summarise documents in Google Drive — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can file outputs into folders in Google Drive — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can export and convert formats in Google Drive — after reading the context and deciding it should.
When a file lands in a folder in Google Drive…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a doc is updated in Google Drive…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a file is shared in Google Drive…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
The Google Calendar and Google Drive hand-off, setup template
Start with the google-calendar-api node and the google-drive-api node. Configure the Google Calendar source payload, the agent input, and the Google Drive 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": "646d7f06-0f46-4b08-aaf5-43bc99be559c",
"name": "Google Calendar → Google Drive",
"nodes": [
{
"id": "087e66da-23b9-495b-ab23-f38fb004b8a2",
"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": "9702a1d8-b5a6-4c00-a5ea-6772dd689eac",
"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 Google Drive, 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": "dd1bd119-7962-48ff-aaa4-6ca8223bef06",
"text": "Configure destination in Google Drive",
"x": 512,
"y": 528,
"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": {}
}
],
"edges": [
{
"id": "ea8fd66f-0319-480c-a4cb-da4b21532e04",
"start": {
"id": "087e66da-23b9-495b-ab23-f38fb004b8a2",
"type": "output"
},
"end": {
"id": "9702a1d8-b5a6-4c00-a5ea-6772dd689eac",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "45d0b895-ecd7-4013-a46f-234a79c0fda2",
"start": {
"id": "9702a1d8-b5a6-4c00-a5ea-6772dd689eac",
"type": "output"
},
"end": {
"id": "dd1bd119-7962-48ff-aaa4-6ca8223bef06",
"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 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.
Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Google Calendar. Install it, point its last step at Google Drive, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
What building this looks like
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Google Calendar takes one OAuth sign-in, Google Drive takes one OAuth sign-in.
- Configure the nodes above, or start from a marketplace workflow and edit it. The agent in the middle is the part worth spending time on.
- Run it once with an approval gate in place. The receipt tells you what it read, what it concluded, and what it changed in Google Drive.
Google Calendar and Google Drive — common questions
Can I connect Google Calendar to Google Drive without writing code?
You can build it entirely from the canvas. Authorise Google Calendar with one OAuth sign-in, Google Drive with one OAuth sign-in, then tell the agent what prep briefings before every meeting should look like once Google Drive 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 Google Drive 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 Google Drive with the reasoning recorded.
Does my Google Calendar and Google Drive 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, Google Drive and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Google Calendar and Google Drive run leave behind?
A receipt: what was read in Google Calendar, which tools ran with which arguments, what the agent concluded, and what it wrote to Google Drive. Anything consequential can sit behind an approval gate so a person signs off before it happens.
