Automate Asana + Gmail
Team tasks, due dates and the follow-through between them. The inbox most operations still start in. 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 Gmail to finish this hand-off.
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 Gmail.
When a task is created or completed in Asana…
…an agent can send or draft a reply in Gmail — after reading the context and deciding it should.
When a due date nears in Asana…
…an agent can apply labels and archive in Gmail — after reading the context and deciding it should.
When a project updates in Asana…
…an agent can extract attachments and fields in Gmail — after reading the context and deciding it should.
When a new email arrives in Gmail…
…an agent can create tasks with owners in Asana — with the reasoning recorded in the run’s receipt.
When a label is applied in Gmail…
…an agent can update status and comments in Asana — with the reasoning recorded in the run’s receipt.
When a thread goes unanswered in Gmail…
…an agent can roll up project summaries in Asana — with the reasoning recorded in the run’s receipt.
Copy this Asana → Gmail workflow
Start with a custom-api call to app.asana.com and the gmail-api node. Configure the Asana source payload, the agent input, and the Gmail 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": "863ae7a6-4c43-4936-a43a-6fc8c6e9a1b8",
"name": "Asana → Gmail",
"nodes": [
{
"id": "202d7689-b54c-47d9-adac-d5461085ee12",
"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": "b0916b65-50b7-424a-a44b-939584e1c43c",
"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 Asana item. Decide whether it warrants action in Gmail, 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": "0e7ce5dd-ceac-4ec2-a2a6-f54db29a08f8",
"text": "Configure destination in Gmail",
"x": 512,
"y": 528,
"isEditing": false,
"type": "gmail-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"operation": "Search and Read Emails",
"searchQuery": "CONFIGURE_SEARCHQUERY",
"maxResults": 1
},
"description": "Setup template for Gmail API. A powerful tool to send, reply, read, organize, and manage attachments in Gmail. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "b63dc7aa-761b-4be3-a53a-68e1351ce0e6",
"start": {
"id": "202d7689-b54c-47d9-adac-d5461085ee12",
"type": "output"
},
"end": {
"id": "b0916b65-50b7-424a-a44b-939584e1c43c",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "289e99d1-36f2-462d-a757-149c1bdd7ba6",
"start": {
"id": "b0916b65-50b7-424a-a44b-939584e1c43c",
"type": "output"
},
"end": {
"id": "0e7ce5dd-ceac-4ec2-a2a6-f54db29a08f8",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Gmail API
A powerful tool to send, reply, read, organize, and manage attachments in Gmail.
- operation — The Gmail operation to perform. Current example:
Search and Read Emails. - searchQuery — Optional. Gmail search query (e.g., 'from:user is:unread'). If blank, fetches latest emails. Current example:
CONFIGURE_SEARCHQUERY. - maxResults — Maximum number of emails to return. Current example:
1.
Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Asana. Install it, point its last step at Gmail, 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
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Asana takes one OAuth sign-in, Gmail takes one OAuth sign-in.
- Configure the nodes above, or start from a marketplace workflow and edit it. The agent in the middle is the part worth spending time on.
- Run it once with an approval gate in place. The receipt tells you what it read, what it concluded, and what it changed in Gmail.
Asana and Gmail — common questions
Can I connect Asana to Gmail without writing code?
You can build it entirely from the canvas. Authorise Asana with one OAuth sign-in, Gmail with one OAuth sign-in, then tell the agent what meeting decisions become assigned tasks should look like once Gmail 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 Gmail automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Asana item in full and decides — whether it matters, how to summarise it, and what belongs in Gmail. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Asana and Gmail data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Asana or Gmail 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 Gmail 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 triage and classify incoming mail, and the exact change applied in Gmail, with approvals attached where you required them.
