Skip to content

How to send email to Asana as a task, and what the task keeps

On this page

To send an email to Asana as a task, forward it to x@mail.asana.com. That’s the literal address, the same for everyone. A task appears in your My Tasks. The subject becomes the task name, the body becomes the description, and the attachments come along. To land it in a project instead, send it to that project’s own address. Asana offers this on every plan it lists, from Personal up. Everything below comes from Asana’s own help center, checked October 5, 2026.

A few details decide whether that works on a busy Tuesday. Asana has to recognize the address you send from. The task has to land where your team will see it. And it helps to know what the task keeps once it’s there.

Three ways an email becomes an Asana task

Asana gives you three routes, plus a fourth for teams on its top plans.

RouteWhere the task landsWhat you set on the way inLater replies in the thread
Forward to x@mail.asana.comYour My TasksNothing. You edit the task afterwardStay in your mailbox
Send to a project’s addressThat projectNothing. You edit the task afterwardStay in your mailbox
Asana for Gmail add-onWherever you chooseName, assignee, due date, description, project, attachmentsAdded as comments if sync is on
Asana for Outlook add-inWherever you chooseAssignee, due date and projectYou add them yourself, as comments
Email Bridge (Enterprise plans)A project, from an intake addressNothing. An admin configures itThe outside sender’s replies become comments

The forwarding address is quickest to start with, since there’s nothing to install. The add-ons take a minute to set up. They let you decide where the task goes before it exists. The rest of this page takes each one in turn.

Forwarding to x@mail.asana.com

Asana publishes exactly how it reads a forwarded email.

Email subject → Task name. Email body → Task description. Email attachments → Task attachments. CC’d email recipients → Task collaborators. From → Task collaborator.

So the task arrives filled in from the message, and anyone you copied is following it. An extra address in the To line becomes a collaborator as well.

Three details decide whether the forward works.

The address you send from has to be on your Asana account. Asana matches the sender to a person. If you forward from a personal Gmail and your Asana login is your work address, add the Gmail to your account first. Asana flags one real risk here:

“adding an email address that is already associated with a different Asana account will result in both accounts being merged. This is an irreversible change.”

If that personal address once signed up for its own Asana trial, the two accounts join for good. Check before you add it.

The task goes to one workspace. If you belong to more than one, Asana uses the one picked in the Email forwarding tab of your settings. A task that seems to vanish has often landed in the other workspace.

The whole email has a 30 MB ceiling. That includes the attachments. A long thread with a few scanned PDFs can pass it.

One more thing: everyone you put in To or CC needs access to that workspace or project. Asana says that otherwise “you may receive a notification indicating that your task could not be created.”

Sending to a project instead of My Tasks

A forward to x@mail.asana.com is captured, and you still have to file it. If the work belongs to a project, send it straight there.

Every Asana project has its own address in the form x+projectID@mail.asana.com. The project ID is the string of numbers in the project’s URL. Asana also shows the full address under the project’s Customize menu, in Emails, labeled “Add tasks via email.” Save it as a contact named after the project, such as “Asana: Henderson remodel.” Then it fills in as you type.

You can email tasks into projects you’re a member of. If both the project and its team are public, you can email in without joining. Otherwise the task won’t be created.

A project address is also where client mail should go if your team plans the work in Asana. Everyone on the project sees the new task, and nobody has to move it out of one person’s list first.

The Gmail add-on, and the replies that follow

The Asana for Gmail add-on sits in Gmail’s side panel, beside the open message. The task gets filled in there, before it exists. According to Asana’s page for the add-on, you can:

  • change the task name
  • add an assignee
  • set a due date
  • add a description
  • add it to a project
  • choose which attachments to bring, if any

The part worth knowing about is email sync. When you create the task, an option called “Sync future replies to this task” is already checked. Leave it on and each new reply in that thread is added to the task as a comment. When the client writes back on Thursday and moves the date, the task shows it.

Asana’s page names the edges:

  • If the thread already has more than five messages, only the five most recent come into the task. Everything after that syncs as it arrives.
  • HTML email turns into plain text in Asana.
  • Anyone added to the task can read the synced messages. Think about that before syncing a thread with a client’s financial details in it.
  • The sync option only shows if your Gmail address matches the address you signed in to the add-on with.

You can stop a sync from the add-on, or by deleting the email attachment on the task. It also works in the Gmail app on a phone, once it’s installed on Gmail on the web. If your Google Workspace admin installs it for the whole domain, Asana says it can take up to 7 days to appear.

The Outlook add-in

Asana for Outlook puts two buttons in the Outlook toolbar: Create Task and Open Asana Add-in. Asana says it needs “an Office 365 subscription and access to Microsoft AppSource.” It runs in Outlook on the web and in recent desktop versions for Windows and Mac.

Creating a task lets you assign it, set a due date and add it to a project, all before it exists. One limit is easy to miss:

“It’s currently only possible to set a due date for a task at creation time.”

So pick the date in the add-in, or plan to change it in Asana later.

The second button handles the reply that comes later. It can put a message on a task that already exists, as a comment. Asana doesn’t describe an automatic sync for Outlook the way it does for Gmail, so each later reply is one you add.

When you first connect it, you’ll be asked to let Asana read the email and its attachments. Asana explains that Microsoft began turning off Exchange Online tokens by default on February 17, 2025, and the add-in needs that permission to import the message.

What the task keeps, and what stays in the mailbox

The task starts as a copy of one message. A few things don’t make the trip.

The date. “We need this before the board meets on the 19th” arrives in the description. The due date field stays empty unless you set it, either in an add-on or in Asana afterward.

The name. The subject line becomes the task name. “RE: FW: Q3 numbers” is a fine thread name and a poor task. Rename it as soon as it lands, with a verb: “Send Q3 numbers to Dana.”

The earlier messages. A forward carries what’s in the forward. If the scope was agreed three messages up, make sure that message is in the quoted text, or note it in the description.

What happens next. A forwarded task doesn’t hear later replies. The Gmail add-on’s sync is the one route that brings them in automatically. With a forward, you’ll need to send the reply on yourself.

This is the friction underneath every email-to-task tool: two lists that don’t know about each other. If that’s the problem you keep hitting, email to task, and where your two lists stop talking makes that case in full.

Turning a shared address like info@ into Asana tasks

Plenty of firms want every email to info@ or support@ to become a task without anyone forwarding it by hand. Asana documents two ways.

A forwarder account. Asana’s help page describes setting up a dedicated mailbox, such as forwarder@yourfirm.com. Add it to Asana as a member of the project, and turn off its notifications. Then have the shared address auto-forward into the project. Asana sums up the result:

“Now, every time forwarder@ receives an email, it will be forwarded to the Asana project and assigned to the forwarding account.”

Each task starts out assigned to the forwarder, so someone reassigns it each morning.

Email Bridge. On Enterprise and Enterprise+ plans, Asana’s Email Bridge does the same job for people outside Asana. A client emails support@yourfirm.com, the message forwards to a project, and a task appears. The client gets a notification from your domain. When they reply, the reply becomes a comment on the task. Setup is an admin job. It means verifying your sending domain with three DNS records, which Asana says can take up to 72 hours. Asana also notes that it supports standard forwarding rules but not simple redirects. It rejects forwarded mail that lacks a valid DKIM signature.

Whatever route you use, think about what’s in the mail before it auto-forwards. Every task in a shared project is visible to the whole project.

When a forward doesn’t turn into a task

Most failures trace back to one of five causes, all from Asana’s own page.

What you seeThe likely cause
No task appearsYou sent from an address that isn’t on your Asana account
The task is in the wrong placeYour Email forwarding setting points at another workspace
A “could not be created” noticeSomeone in To or CC doesn’t have access to the workspace or project
An error about misaligned addressesYour mail server’s envelope domain doesn’t match your From address. Your mail admin can fix it
A forward with large attachments failsThe email is over 30 MB

The misaligned-address error is the one people rarely expect. Asana checks this to stop spoofed mail creating tasks in your workspace. It’s a one-time fix on the mail server, so forward the error message to whoever runs your email.

If the task you need is one you haven’t opened yet

Every route above starts with you. You read the message, decide it’s work, and send it on. That works well for the email you got to. It can’t help with the one still sitting at the bottom of the inbox.

Point starts from the message itself. It’s a complete email client that connects to your Gmail or Microsoft 365 account. When a client asks for something, Point drafts a task with the date pulled from their sentence, joined to the thread it came from. Out of the box, the task waits for you to approve it, and you can change that setting for tasks alone. Point’s tasks live in Point. If your team plans its work in Asana, the project address above still has a job. Email task management, without writing it down explains how Point finds a request in a message. The benefits page shows the rest of a day with it.

Common questions

What is Asana’s email address for creating tasks?

It’s x@mail.asana.com, and Asana says the x isn’t a variable. Everyone uses the same address. Asana works out whose task it is from the address you send from. To create the task in a project, use x+projectID@mail.asana.com with that project’s ID. Checked October 5, 2026.

Can I forward an email to a specific Asana project?

Yes. Every project has its own address, shown under the project’s Customize menu in Emails. You need to be a member of the project, unless both the project and its team are public.

Can I assign the task or set a due date when I forward it?

Not with the forwarding address. Anyone you CC becomes a collaborator, and you set the assignee and date in Asana afterward. Both add-ons let you set an assignee and a due date before the task is created.

Do attachments come through when I email a task to Asana?

Yes. Attachments on the email become attachments on the task, as long as the whole email is under 30 MB. The Gmail add-on lets you pick which attachments to bring.

Will replies to the email show up on the Asana task?

Only with the Gmail add-on’s sync turned on, which it is by default. With the Outlook add-in, you add each reply to the task yourself. A forwarded task doesn’t receive later replies at all. If a forwarded request was handed to a colleague, keeping track of their side is covered in tracking what you handed off.

Why didn’t my forwarded email create a task?

The usual cause is sending from an address that isn’t on your Asana account. Next most likely: the task landed in another workspace, someone in CC lacks access, or the email is over 30 MB. If you see an error about misaligned addresses, it’s a mail server setting for your email admin.

Can I comment on an Asana task by email?

Yes. Reply to an Asana notification email and your reply becomes a comment. Put a teammate’s address in the To line to assign the task, or in CC to add them as a collaborator.

Does emailing tasks to Asana work on the free plan?

Asana lists the feature on its Personal plan as well as its paid plans. Email Bridge, for mail from people outside Asana, is listed on Enterprise and Enterprise+ only. Checked October 5, 2026.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.