Automate Google Calendar + Google Sheets
The shared clock your workflows can read and write. The database every team already has open. 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 Sheets 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 Google Sheets.
When an event starts or ends in Google Calendar…
…an agent can append and update rows in Google Sheets — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can read ranges for reporting in Google Sheets — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can maintain a rolling dashboard tab in Google Sheets — after reading the context and deciding it should.
When a row is added or edited in Google Sheets…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a sheet crosses a threshold in Google Sheets…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a schedule fires in Google Sheets…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
The Google Calendar and Google Sheets hand-off, setup template
Start with the google-calendar-api node and the google-sheets-api node. Configure the Google Calendar source payload, the agent input, and the Google Sheets 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": "b1ec0495-cf09-495e-a9ec-e8df81a97dbc",
"name": "Google Calendar → Google Sheets",
"nodes": [
{
"id": "0e18363c-0883-4c47-adf1-3dd7cf6e990e",
"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": "92224eef-e545-4814-a43e-141195fb5e24",
"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 Sheets, 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": "29dde41c-25b8-48f2-abc5-9e8e3362eee8",
"text": "Configure destination in Google Sheets",
"x": 512,
"y": 528,
"isEditing": false,
"type": "google-sheets-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"operation": "Read",
"spreadsheetId": "CONFIGURE_SPREADSHEETID",
"range": "CONFIGURE_RANGE"
},
"description": "Setup template for Google Sheets API. Interact with Google Sheets to read, write, append, or clear data in a spreadsheet. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "bcc3a317-8b62-4995-ab64-eedae06d72b6",
"start": {
"id": "0e18363c-0883-4c47-adf1-3dd7cf6e990e",
"type": "output"
},
"end": {
"id": "92224eef-e545-4814-a43e-141195fb5e24",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "254bb43b-3510-434d-aa22-9dd2dcb592ee",
"start": {
"id": "92224eef-e545-4814-a43e-141195fb5e24",
"type": "output"
},
"end": {
"id": "29dde41c-25b8-48f2-abc5-9e8e3362eee8",
"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 Sheets API
Interact with Google Sheets to read, write, append, or clear data in a spreadsheet.
- operation — The operation to perform on the Google Sheet Current example:
Read. - spreadsheetId — The ID of the Google Sheet to interact with Current example:
CONFIGURE_SPREADSHEETID. - range — The range of cells to interact with (e.g., 'Sheet1!A1:B5') Current example:
CONFIGURE_RANGE.
Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Google Calendar. Install it, point its last step at Google Sheets, 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 Google Sheets
- Download AGNT Community Core — free and local-first.
- Connect Google Calendar with one OAuth sign-in and Google Sheets with one OAuth sign-in; both land in the local vault.
- Start from a marketplace workflow, or drop google-calendar-api and google-sheets-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 Calendar and what was written to Google Sheets.
Google Calendar and Google Sheets — common questions
Can I connect Google Calendar to Google Sheets without writing code?
No code is required. Add both connections in the vault (Google Calendar uses one OAuth sign-in, Google Sheets 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 Calendar to Google Sheets automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Google Sheets, the agent can weigh what arrived from Google Calendar, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Calendar and Google Sheets data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: Google Calendar, Google Sheets, and your chosen model provider — which can be a local one.
What does a Google Calendar and Google Sheets run leave behind?
Every run is recorded end to end — the Google Calendar items examined, the decision and its reasoning, the resulting Google Sheets write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
