AI agents for Google Calendar
The shared clock your workflows can read and write. AGNT connects to Google Calendar so agents can read what happens there, reason about it, and act — with a receipt for every run.
Meeting Follow-Through is a ready-made agent that works in Google Calendar — free, and it runs on your machine.
Google Calendar and AGNT, in brief
| What it does | Lets an AGNT agent read from and act in Google Calendar. |
|---|---|
| Connects with | One OAuth sign-in |
| AGNT node | google-calendar-api, google-calendar-new-event, google-calendar-event-starting |
| Runs when | An event starts or ends |
| Typical build time | Two minutes |
| Where data goes | Nowhere by default — AGNT runs on your machine and credentials never leave it. |
What you can automate
Reacts when…
- an event starts or ends
- a meeting is created
- a day begins
Agents can…
- create or move events
- add agendas to invites
- block focus time
Teams use it for
- prep briefings before every meeting
- post-meeting follow-up on autopilot
- schedule work around real availability
The Google Calendar workflow, ready to paste
Take the simplest useful version: an event starts or ends in Google Calendar. Instead of a rule firing blindly, an agent reads the item in full, works out whether it matters and what it means, and then decides whether to create or move events. Over a week that turns prep briefings before every meeting from something a person checks into something that reports to a person.
Three nodes carry that: something happens in Google Calendar, an agent reads it and forms a view, and it acts only where that view says it should. The definition below is the whole thing — paste it into a new workflow and it loads exactly as drawn.
{
"id": "d2374439-e41f-4d6b-ab40-79a0b1a8761a",
"name": "Google Calendar — read, decide, act",
"nodes": [
{
"id": "4fa58945-0702-4473-a8a2-eaa8e08fc13e",
"text": "Watch Google Calendar for activity",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-calendar-new-event",
"icon": "clock",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Listen for events created or updated on a Google Calendar and trigger the workflow.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "b3895ca2-050b-4f57-ae2c-d98b6e406a76",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "agnt",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Google Calendar item and decide whether it warrants action. Explain your reasoning."
},
"description": "Judges the Google Calendar item against criteria you wrote in plain language.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "22814483-caa4-474a-a47f-de1dbcf43d14",
"text": "Act in Google Calendar",
"x": 512,
"y": 528,
"isEditing": false,
"type": "google-calendar-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "LIST_EVENTS"
},
"description": "Runs LIST_EVENTS on your behalf.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "39253f78-5d83-43a7-ac60-b233f8c6220e",
"start": {
"id": "4fa58945-0702-4473-a8a2-eaa8e08fc13e",
"type": "output"
},
"end": {
"id": "b3895ca2-050b-4f57-ae2c-d98b6e406a76",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "cbbf5bef-9b58-4b8e-a583-c3f369ea1f94",
"start": {
"id": "b3895ca2-050b-4f57-ae2c-d98b6e406a76",
"type": "output"
},
"end": {
"id": "22814483-caa4-474a-a47f-de1dbcf43d14",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}
Install Meeting Follow-Through — it runs on Google Calendar
Meeting Follow-Through is a working agent that uses Google Calendar. Installing it drops the whole workflow onto your canvas — connected, editable, and yours to change.
Runs on your own machine · See what it does
A calendar is a schedule of things to prepare for
Most calendar automation stops at reminders, which is the least useful thing a calendar can trigger. The valuable pattern is preparation: a meeting on the calendar is advance notice that a briefing should be researched, an agenda drafted, and the relevant history assembled before anyone joins.
Closing the loop afterwards
The same integration handles the other end. Once a meeting finishes, its follow-up can be drafted, decisions filed and actions created in your tracker — so a calendar entry becomes the anchor for the work either side of it rather than just a block of time.
Inside the Google Calendar API node
Interact with Google Calendar to manage events, check availability, and create Google Meet meetings.
What it can do: LIST_EVENTS GET_EVENT CREATE_EVENT CREATE_MEET_EVENT UPDATE_EVENT DELETE_EVENT QUICK_ADD GET_FREE_BUSY LIST_CALENDARS RESPOND_TO_EVENT
Full Google Calendar API parameter reference
| Parameter | Type | What it does |
|---|---|---|
actionrequired |
string | The action to perform on Google Calendar LIST_EVENTS · GET_EVENT · CREATE_EVENT · CREATE_MEET_EVENT · UPDATE_EVENT · DELETE_EVENT · QUICK_ADD · GET_FREE_BUSY |
calendarId |
string | Calendar ID (defaults to 'primary') only when action is LIST_EVENTS or GET_EVENT or CREATE_EVENT or CREATE_MEET_EVENT |
eventId |
string | The ID of the event only when action is GET_EVENT or UPDATE_EVENT or DELETE_EVENT or RESPOND_TO_EVENT |
summary |
string | Event title only when action is CREATE_EVENT or CREATE_MEET_EVENT or UPDATE_EVENT |
description |
string | Event description only when action is CREATE_EVENT or CREATE_MEET_EVENT or UPDATE_EVENT |
location |
string | Event location only when action is CREATE_EVENT or CREATE_MEET_EVENT or UPDATE_EVENT |
startTime |
string | Start time (ISO 8601, e.g. 2026-07-20T14:00:00-07:00) or YYYY-MM-DD for all-day only when action is CREATE_EVENT or CREATE_MEET_EVENT or UPDATE_EVENT or GET_FREE_BUSY |
endTime |
string | End time (ISO 8601) or YYYY-MM-DD for all-day only when action is CREATE_EVENT or CREATE_MEET_EVENT or UPDATE_EVENT or GET_FREE_BUSY |
timeZone |
string | IANA time zone (e.g. America/Los_Angeles). Defaults to calendar's zone. only when action is CREATE_EVENT or CREATE_MEET_EVENT or UPDATE_EVENT |
attendees |
string | Comma-separated attendee emails only when action is CREATE_EVENT or CREATE_MEET_EVENT or UPDATE_EVENT |
sendUpdates |
string | Whether to email attendees about the change (default: none) none · all · externalOnly only when action is CREATE_EVENT or CREATE_MEET_EVENT or UPDATE_EVENT or DELETE_EVENT |
quickAddText |
string | Natural language event text, e.g. 'Lunch with Sam Friday 1pm' only when action is QUICK_ADD |
6 further parameters are available on the node itself.
Every parameter above is read from the shipped google-calendar-api node, so it cannot drift from the product.
Connect Google Calendar in two minutes
- Download AGNT Community Core — free, local-first, no account needed to run.
- Connect with one OAuth sign-in from AGNT’s vault — tokens are stored encrypted on your machine and never leave it.
- Drop the Google Calendar node into a workflow or hand it to an agent — the first run produces a receipt you can read line by line.
Google Calendar + AGNT — common questions
What can trigger a workflow from the calendar?
An event starting or ending, a meeting being created, or the start of a day — each can begin a run.
Can agents create or move events?
Yes, including blocking focus time and scheduling around real availability.
Does it work with shared team calendars?
Yes, subject to the permissions the connected account already has.