Automate Asana + Google Drive
Team tasks, due dates and the follow-through between them. Where the documents live — and pile up. 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 Asana; point its last step at Google Drive to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Asana side, works out what it means, and only then decides what — if anything — should happen in Google Drive.
When a task is created or completed in Asana…
…an agent can read and summarise documents in Google Drive — after reading the context and deciding it should.
When a due date nears in Asana…
…an agent can file outputs into folders in Google Drive — after reading the context and deciding it should.
When a project updates in Asana…
…an agent can export and convert formats in Google Drive — after reading the context and deciding it should.
When a file lands in a folder in Google Drive…
…an agent can create tasks with owners in Asana — with the reasoning recorded in the run’s receipt.
When a doc is updated in Google Drive…
…an agent can update status and comments in Asana — with the reasoning recorded in the run’s receipt.
When a file is shared in Google Drive…
…an agent can roll up project summaries in Asana — with the reasoning recorded in the run’s receipt.
Copy this Asana → Google Drive workflow
Asana is reached through a custom-api call to app.asana.com and Google Drive through the google-drive-api node. Between them sits the agent, which is the part a field-mapping tool cannot do: it reads the item and decides whether the hand-off is warranted at all.
{
"id": "f9267ce3-c905-40dd-a2dd-69dcba389186",
"name": "Asana → Google Drive",
"nodes": [
{
"id": "c9211932-1e62-4d03-a8cc-30fd95c96c66",
"text": "Poll Asana",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"interval": "15",
"unit": "minutes"
},
"description": "Checks Asana on a schedule.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "3444e3f5-dfc2-46d5-ab41-62da1ecb59fa",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Asana item. Decide whether it warrants action in Google Drive, and explain why."
},
"description": "Decides whether this Asana item warrants anything in Google Drive.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "e48f7c03-6b4e-46a2-a89f-02fb9d168af8",
"text": "Act in Google Drive",
"x": 512,
"y": 528,
"isEditing": false,
"type": "google-drive-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "LIST_FILES"
},
"description": "Interact with Google Drive to perform various operations on files and folders.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "2ce5938d-22af-414b-ad40-9688e34ab88e",
"start": {
"id": "c9211932-1e62-4d03-a8cc-30fd95c96c66",
"type": "output"
},
"end": {
"id": "3444e3f5-dfc2-46d5-ab41-62da1ecb59fa",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "b380b27b-31d3-49fe-a9f4-ca6b2f01c7e8",
"start": {
"id": "3444e3f5-dfc2-46d5-ab41-62da1ecb59fa",
"type": "output"
},
"end": {
"id": "e48f7c03-6b4e-46a2-a89f-02fb9d168af8",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Asana. Install it, point its last step at Google Drive, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
What building this looks like
- Download AGNT Community Core — free and local-first.
- Connect Asana with one OAuth sign-in and Google Drive with one OAuth sign-in; both land in the local vault.
- Start from a marketplace workflow, or drop a custom-api node and google-drive-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 Asana and what was written to Google Drive.
Asana and Google Drive — common questions
Can I connect Asana to Google Drive without writing code?
No code is required. Add both connections in the vault (Asana uses one OAuth sign-in, Google Drive 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 Asana to Google Drive automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Google Drive, the agent can weigh what arrived from Asana, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Asana and Google Drive data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to Asana, Google Drive and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Asana and Google Drive run leave behind?
Every run is recorded end to end — the Asana items examined, the decision and its reasoning, the resulting Google Drive write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
