Automate Google Calendar + Notion
The shared clock your workflows can read and write. The team wiki agents can actually keep current. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Meeting Follow-Through already works across Google Calendar and Notion — free, and it runs on your machine.
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 Notion.
When an event starts or ends in Google Calendar…
…an agent can create and update pages in Notion — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can write database rows in Notion — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can append meeting notes in Notion — after reading the context and deciding it should.
When a page is created or edited in Notion…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a database row changes in Notion…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a status flips in Notion…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
The Google Calendar and Notion hand-off, setup template
Start with the google-calendar-api node and the notion-api node. Configure the Google Calendar source payload, the agent input, and the Notion 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": "117daabd-dedf-4158-ad3b-84b5daf753b8",
"name": "Google Calendar → Notion",
"nodes": [
{
"id": "29a44783-33d5-474f-a2c1-e2c2945a9eca",
"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": "cc7e5116-c031-4912-ac2c-616afe0b2b44",
"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 Notion, 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": "02347949-62ec-48ec-a2cc-aff75670c814",
"text": "Configure destination in Notion",
"x": 512,
"y": 528,
"isEditing": false,
"type": "notion-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"operation": "search",
"pageSize": 1,
"query": "CONFIGURE_QUERY",
"filterType": "all"
},
"description": "Setup template for Notion API. Interact with Notion - search, query databases, get pages, and create pages. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "19d8c33c-d411-4a3f-acff-28ffb33ccff2",
"start": {
"id": "29a44783-33d5-474f-a2c1-e2c2945a9eca",
"type": "output"
},
"end": {
"id": "cc7e5116-c031-4912-ac2c-616afe0b2b44",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "8128d70a-a1ee-4e8d-aa85-3ae5ccedaf82",
"start": {
"id": "cc7e5116-c031-4912-ac2c-616afe0b2b44",
"type": "output"
},
"end": {
"id": "02347949-62ec-48ec-a2cc-aff75670c814",
"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 Notion API
Interact with Notion - search, query databases, get pages, and create pages.
- operation — Operation to perform Current example:
search. - query — Search query text Current example:
CONFIGURE_QUERY. - filterType — Filter results by type Current example:
all. - pageSize — Max results (default: 10-100) Current example:
1.
Install Meeting Follow-Through
Meeting Follow-Through already uses both Google Calendar and Notion, 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
Build it in AGNT
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Notion (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 notion-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 Notion — common questions
Can I connect Google Calendar to Notion without writing code?
You can build it entirely from the canvas. Authorise Google Calendar with one OAuth sign-in, Notion with one OAuth sign-in, then tell the agent what prep briefings before every meeting should look like once Notion 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 Notion automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Google Calendar item in full and decides — whether it matters, how to summarise it, and what belongs in Notion. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Google Calendar and Notion data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Google Calendar or Notion tokens. The runtime talks directly to both services. Choose a local model and the content of what it reads never leaves the machine at all.
What does a Google Calendar and Notion 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 meeting notes filed where they belong, and the exact change applied in Notion, with approvals attached where you required them.
