Automate Asana + Google Calendar
Team tasks, due dates and the follow-through between them. The shared clock your workflows can read and write. 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 Asana and Google Calendar — 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 Asana into Google Calendar.
When a task is created or completed in Asana…
…an agent can create or move events in Google Calendar — after reading the context and deciding it should.
When a due date nears in Asana…
…an agent can add agendas to invites in Google Calendar — after reading the context and deciding it should.
When a project updates in Asana…
…an agent can block focus time in Google Calendar — after reading the context and deciding it should.
When an event starts or ends in Google Calendar…
…an agent can create tasks with owners in Asana — with the reasoning recorded in the run’s receipt.
When a meeting is created in Google Calendar…
…an agent can update status and comments in Asana — with the reasoning recorded in the run’s receipt.
When a day begins in Google Calendar…
…an agent can roll up project summaries in Asana — with the reasoning recorded in the run’s receipt.
Copy this Asana → Google Calendar workflow
Asana is reached through a custom-api call to app.asana.com and Google Calendar through the google-calendar-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": "d4d4778f-7ff4-46ef-a331-90aeb47b7b8e",
"name": "Asana → Google Calendar",
"nodes": [
{
"id": "7972af37-cf2d-464e-ad36-cfb7874f8c6c",
"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": "ee58b204-054f-445d-a50b-01bd7cfe4fce",
"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 Calendar, and explain why."
},
"description": "Decides whether this Asana item warrants anything in Google Calendar.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "5af76441-4438-4604-aa79-e009021a2028",
"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": "Interact with Google Calendar to manage events, check availability, and create Google Meet meetings.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "86cb93ea-95ec-4975-abf0-6e15083f9e46",
"start": {
"id": "7972af37-cf2d-464e-ad36-cfb7874f8c6c",
"type": "output"
},
"end": {
"id": "ee58b204-054f-445d-a50b-01bd7cfe4fce",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "2e8b4133-5873-4328-aa2d-47995cf1612c",
"start": {
"id": "ee58b204-054f-445d-a50b-01bd7cfe4fce",
"type": "output"
},
"end": {
"id": "5af76441-4438-4604-aa79-e009021a2028",
"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 already uses both Asana and Google Calendar, 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
What building this looks like
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Google Calendar (one OAuth sign-in) and Asana (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; custom-api does the reading and google-calendar-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
Asana and Google Calendar — common questions
Can I connect Asana to Google Calendar without writing code?
You can build it entirely from the canvas. Authorise Asana with one OAuth sign-in, Google Calendar with one OAuth sign-in, then tell the agent what meeting decisions become assigned tasks should look like once Google Calendar 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 Asana to Google Calendar automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles meeting decisions become assigned tasks the way a colleague would — reading the Asana context, judging it, then writing to Google Calendar with the reasoning recorded.
Does my Asana and Google Calendar data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Asana or Google Calendar 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 Asana and Google Calendar run leave behind?
You get an auditable trail rather than a success flag. It shows the Asana context the agent worked from, the judgment it made about prep briefings before every meeting, and the exact change applied in Google Calendar, with approvals attached where you required them.
