Connect Asana to Cortex

Workplace connections

Asana

Content and access

Tasks, subtasks, and comments from the Asana projects the token can see. Every task keeps who can see it in Asana.

Before you begin

Use Cortex admin access and organization-wide connection requirements, plus these source-specific permissions:

Set up Asana

Choose the token first, because it decides what reaches Cortex:

• Service Account (recommended): on Asana Enterprise, a super admin creates one under Admin console → Apps → Service accounts. It reads every project in the workspace, including private ones.
• Personal access token: any member can create one in the Asana developer console (app.asana.com/0/my-apps). It reads only what its owner can see, so private projects the owner is not a member of do not sync.

1. Create the token in Asana and copy it.
2. In Cortex, open Organization → Apps, select Add connection, and choose Asana under Source. Paste the token into Asana token.
3. If the token can see more than one Asana workspace, enter the ID of the one to connect in Workspace ID (only if your token sees several workspaces). Otherwise, leave it blank.
4. Select Connect. Then open the connection's Manage menu and select Test & preview. The preview shows the workspace, how many projects the token can see, and a sample of projects marked Public or Private.

You can also connect Asana in the Connect apps step of onboarding.

Asana scope and limits

Each read-only connection covers one Asana workspace. Cortex reads every project the token can see, except archived projects. When you connect, it reads open tasks and tasks completed in the last 90 days, with their subtasks and comments. After that, it picks up every task that changes. Portfolios and Goals are not synced. To connect a different workspace, delete the connection and add a new one.

For each task, Cortex stores its name, description, custom field values, status, assignee, projects, sections, up to 100 comments, and a link back to Asana. Every task keeps who can see it in Asana: a task in a public project is visible to the whole workspace; otherwise, access comes from the members and teams of its private projects, its assignee, and its followers. A subtask also keeps its parent task's access.

Changes sync about every hour. Tasks deleted in Asana, and changes to project membership or privacy, are picked up within about an hour. A daily safety check catches any change the hourly sync missed.

Asana access is the security boundary: Cortex reads only what the token can see. A personal access token usually covers fewer projects than a Service Account. To check coverage, compare the visible project count and the private projects in Test & preview with what you expect.

Manage this connection

To replace the token, select Edit connection. Revoking the connection removes its synced Asana tasks from Cortex.

See the shared connection management guide for credential updates, reauthorization, and revocation.