---
title: "Connect a project to Asana"
description: "Hand each new task of a project over to Asana as an Asana project: the Asana consent, choosing the workspace and the team, and how assignees are added"
category: integrations
section: native-integrations
type: Tutorial
lastUpdated: 2026-09-30
locale: en
canonical: https://support.talkspirit.com/en/integrations/connect-a-project-to-asana
---

# Connect a project to Asana


> **In summary:** open the project’s settings, then the **Integrations** tab, and select **Connect** on the **Asana** card. Asana asks for your consent on its own screen. Back on the project, choose a **Workspace** and a **Team**, then **Confirm destination**. Each new task becomes an Asana **project** in that team, and its assignees found in Asana become project members.

This guide covers Asana. How the hand-off works, which tasks are sent and why a project holds one project tool at a time is the same for every tool: see [Connect a project to a project tool](/integrations/connect-a-project-to-a-project-tool).

## A task becomes an Asana project

In Asana, a Talkspirit task becomes a **project**, not an Asana task. This is why the destination stops at a team: the project is what Talkspirit creates.

## Before you start

- You are an **owner or editor** of the project in Talkspirit.
- You have an Asana account that can create projects in the team you want. Every Asana project is created with this account.
- The project is not connected to another project tool. If it is, disconnect that one first.

## Connect the project

1. Open the project’s settings, then the **Integrations** tab.
2. On the **Asana** card, select **Connect**.
3. Asana shows its consent screen. Sign in if asked, and approve: Talkspirit asks for full access to your Asana account, which adding and removing project members requires.
4. You return to the project. The card reads **Choose a destination**.
5. Choose the **Workspace**, then the **Team**, and select **Confirm destination**.

The card reads **Connected** and names the destination as *Workspace → Team*.

To send tasks to another team, select **Change destination**. No new consent is needed.

## What a project carries

| Asana project field | Filled with |
| --- | --- |
| Name | The task's title |
| Description | The task's description, with bold, italic, code, links and lists kept. Headings become bold text: Asana accepts fewer formats in a project description than in a task |
| Members | The task's assignees found in Asana, see below |
| Due date | Nothing |

The Asana project does not link back to the Talkspirit task. Once Asana confirms the project, the task is marked done in Talkspirit and shows an **Open in Asana** link to the project.

## How assignees become members

Talkspirit looks each assignee up in Asana by **email address**, and keeps a match only when Asana returns the same address. Every confirmed person is added to the Asana project as a member.

- An assignee who is not found is skipped. The others are still added.
- If Asana refuses to add the members, the Asana project is still created, without them.
- A role or a circle assigned to the task is not sent: it has no email address.

The account that connected Asana is not left on every Asana project. Talkspirit creates each Asana project without an owner, then removes that account from its members, unless that person is one of the task's assignees. If Asana refuses the removal, the account stays a member of that project.

## When Asana projects are not created

When sending stops, the card on the project reads **Interrupted** and an alert says why and what to do: see [Connect a project to a project tool](/integrations/connect-a-project-to-a-project-tool).

| What you see | Likely cause | What to do |
| --- | --- | --- |
| The card reads **Interrupted**: *Access to Asana was withdrawn.* | The consent was withdrawn in Asana | **Disconnect** Asana and connect it again |
| The card reads **Interrupted**: *5 deliveries failed in a row.* | Asana refused five projects in a row, for example because your account can no longer create projects in the team | **Change destination** and choose the team again, or disconnect Asana and connect it again |
| Asana projects arrive without their members, and the account that connected Asana stays a member of each one, on a project connected to Asana early on | The consent was given before Talkspirit asked for full access. Asana does not extend a consent already given | **Disconnect**, then **Connect** again and choose the destination |
| One task was not marked done, the next ones were | Asana was busy and refused that one request | Create that Asana project by hand. The following tasks are not affected |
| An Asana project arrived without some of its members | Those assignees use a different email address in Asana | Add them in Asana |
| **Connect** cannot be selected | Another project tool is connected to the project | Its tooltip names it: disconnect it first |

Tasks created while sending was interrupted are not sent later.

## What’s next?

- [Connect a project to a project tool](/integrations/connect-a-project-to-a-project-tool): the hand-off, which tasks are sent, and one tool per project.
- [Connect a project to Trello](/integrations/connect-a-project-to-trello)
- [Connect a project to Jira](/integrations/connect-a-project-to-jira)
- [Connect a project to Basecamp](/integrations/connect-a-project-to-basecamp)