I was recently helping a friend get setup for GTD and Asana, starting from scratch. We got to the Clarify step, and I insisted he take the time to clear his email inbox by routing actionable items into Asana. He pushed back immediately: “This feels like pushing paper.”
I didn’t give him a choice. I told him if he wanted my help, he’d have to at least try it my way. “Give me one week,” I said. One week later, a message arrived.
Why the inbox is the wrong place for commitments
Your email inbox is not a to-do list.
An email is not a task. The subject line “Re: vendor quote” is not a clearly defined next action. And yet most of us use our inboxes exactly this way — flagging messages, leaving them unread, scrolling back each morning to re-decide what they mean. Every time you return to the same email, you’re spending energy you already spent once. You’re not moving it forward. You’re just touching it again.
The value of routing email into Asana isn’t that your inbox looks cleaner. It’s that you’re forced to do two things GTD calls Clarifying and Organizing: deciding what this email actually requires (what’s the specific next action?), and putting it where all your other commitments live (one system, not two).
Tiago Forte frames the underlying problem well: “The main reason your inbox is overflowing is the same reason any system gets blocked at the intake: a lack of effective downstream systems. Things pile up when they have nowhere to go.” Email is a capture point. It’s not a place for commitments to live.
The setup: how I actually do it
Asana gives every user a unique email address per destination — one for My Tasks, and separate ones for individual projects. Forward an email to any of these and it becomes a task, with the subject line as the task name and the body as the description.
That’s the whole setup:
-
In any project, hit the drop-down menu next to the project name then go to Import → Email to get the address. For My Tasks, you can just use x@mail.asana.com.
-
Save the addresses to your contact list as real contacts. I have: “Asana - My Tasks,” “Asana - Waiting For” (a project for items I’m waiting on from others), and several other project inboxes I add to regularly, or needed temporarily.
-
Forward emails using standard keyboard shortcuts. No plugin. No context switch.
The subject line that arrives as the task name is almost always wrong. “Re: duplicate barcode” isn’t a task. “Review UPC vs GTIN1 in Group B” is. That rewriting step — enabled by the forwarding action — is where the value actually comes from. You’re clarifying, not just moving.
What works: The keyboard shortcut flow. Zero friction once it’s set up. No plugin to load, no extra tab to open.
What I’d do differently: Name the contacts clearly from the start. “Asana — My Tasks” not “x+12345678@mail.asana.com.” You’ll build up several of these, and the addresses are indistinguishable without labels.
Pro tip — multiple domains: By default, Asana only accepts forwarded emails from the address registered in your account. If you use multiple email addresses like me, you can add them all in Settings → Email Forwarding. You can even add multiple domains — but you need to own the domains and be able to add a DNS TXT record to verify each one. Once verified, forwarding works from any of them.
Pro tip — rules: The email-to-task method pairs well with Asana’s rules engine. Set up a rule in any project to trigger on task creation and you can automatically reassign the task, add collaborators, set a due date, move it to the right section, or apply a tag — without touching it manually. The email creates the task; the rule does the triage.
The plugins
The Outlook add-in is slow, logs out constantly, and requires too many clicks. I’ve tried it. Others in the community have confirmed the same. I don’t recommend it as a primary workflow.
The Gmail plugin is better — fewer clicks, less friction, and it keeps you inside Gmail’s visual environment. If you prefer clicking through a workflow over keyboard shortcuts, it’s a valid option. This post covers the Gmail setup step-by-step and is worth reading if you go that route.
Forward-to-task wins for keyboard-driven users. The Gmail plugin wins for visual/click-through users.
I helped my friend install the Gmail plugin, but also taught him forward-to-task. His take?
“The Asana Gmail integration is fire. Just started working for me.”
Pick the method that reduces friction enough that you’ll actually do it consistently.
Lessons
-
The inbox needs a downstream system or it will always fill back up. Email is intake, not storage. The moment you start treating subject lines as tasks, you’ve lost.
-
Friction determines adoption. My friend didn’t use my method. He used the one that worked for him. The right setup is the one you’ll actually do consistently.
-
The clarifying step is where the value lives. Forwarding the email is just the trigger. Rewriting the subject line into a real next action is the work.
Over to you
How do you route actionable email into Asana?
-
If you’re using the Outlook add-in and it’s actually working for you, I’d genuinely like to know — I’ve never gotten it to behave.
-
If you’ve built automation around this (Power Automate, Zapier, email rules), what does the trigger look like?
-
If you haven’t set this up yet — what’s the friction point holding you back?