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, setup template
Start with the google-drive-api node and the notion-api node. Configure the Google Drive 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": "22d106fe-b884-4200-a68d-bcee84b254bc",
"name": "Google Drive → Notion",
"nodes": [
{
"id": "cc760526-659d-4c2f-a7a9-1617f2ea8f72",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "587bedb5-ea29-429a-a8f5-297f80a9aa7c",
"text": "Read Google Drive",
"x": 512,
"y": 336,
"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": {}
},
{
"id": "a2b651e9-f0c2-45d5-a7eb-8ed209bbbeca",
"text": "Review source and draft",
"x": 512,
"y": 528,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Google Drive 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": "301331d6-9208-47be-acfd-7b3c364c4d1c",
"text": "Configure destination in Notion",
"x": 512,
"y": 720,
"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": "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
},
{
"id": "7b9259e5-0a40-4776-af10-7509c4e287f4",
"start": {
"id": "a2b651e9-f0c2-45d5-a7eb-8ed209bbbeca",
"type": "output"
},
"end": {
"id": "301331d6-9208-47be-acfd-7b3c364c4d1c",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}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.
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 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.
