Automate Google Drive + Notion
Where the documents live — and pile up. 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.
Content Producer already works across Google Drive and Notion — free, and it runs on your machine.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from Google Drive into Notion.
When a file lands in a folder in Google Drive…
…an agent can create and update pages in Notion — after reading the context and deciding it should.
When a doc is updated in Google Drive…
…an agent can write database rows in Notion — after reading the context and deciding it should.
When a file is shared in Google Drive…
…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 read and summarise documents in Google Drive — with the reasoning recorded in the run’s receipt.
When a database row changes in Notion…
…an agent can file outputs into folders in Google Drive — with the reasoning recorded in the run’s receipt.
When a status flips in Notion…
…an agent can export and convert formats in Google Drive — with the reasoning recorded in the run’s receipt.
Google Drive to Notion, in three nodes
The two ends are the google-drive-api node and the notion-api node. What makes this different from a zap is the middle node — it forms a view about the Google Drive item before anything reaches Notion.
{
"id": "22d106fe-b884-4200-a68d-bcee84b254bc",
"name": "Google Drive → Notion",
"nodes": [
{
"id": "cc760526-659d-4c2f-a7a9-1617f2ea8f72",
"text": "Watch Google Drive",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-drive-api",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Interact with Google Drive to perform various operations on files and folders.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "587bedb5-ea29-429a-a8f5-297f80a9aa7c",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Google Drive item. Decide whether it warrants action in Notion, and explain why."
},
"description": "Decides whether this Google Drive item warrants anything in Notion.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "a2b651e9-f0c2-45d5-a7eb-8ed209bbbeca",
"text": "Act in Notion",
"x": 512,
"y": 528,
"isEditing": false,
"type": "notion-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "search"
},
"description": "Interact with Notion - search, query databases, get pages, and create pages.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "ae005fbc-08e8-444e-aa02-b112eca68808",
"start": {
"id": "cc760526-659d-4c2f-a7a9-1617f2ea8f72",
"type": "output"
},
"end": {
"id": "587bedb5-ea29-429a-a8f5-297f80a9aa7c",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "10fb6f01-da82-4c15-ad4a-1276ef193bc2",
"start": {
"id": "587bedb5-ea29-429a-a8f5-297f80a9aa7c",
"type": "output"
},
"end": {
"id": "a2b651e9-f0c2-45d5-a7eb-8ed209bbbeca",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Content Producer
Content Producer already uses both Google Drive 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
- Download AGNT Community Core — free and local-first.
- Connect Google Drive with one OAuth sign-in and Notion with one OAuth sign-in; both land in the local vault.
- Start from a marketplace workflow, or drop google-drive-api and notion-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 Drive and what was written to Notion.
Google Drive and Notion — common questions
Can I connect Google Drive to Notion without writing code?
Yes. Google Drive connects with one OAuth sign-in and Notion with one OAuth sign-in, both from the local credential vault. You then describe the job in plain language — “when a file lands in a folder, create and update pages” — and the agent handles the rest.
How is this different from a field-mapping Google Drive to Notion automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Google Drive 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 Drive and Notion data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Google Drive 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 Drive and Notion run leave behind?
A receipt: what was read in Google Drive, which tools ran with which arguments, what the agent concluded, and what it wrote to Notion. Anything consequential can sit behind an approval gate so a person signs off before it happens.
