Skip to main content
Asana is a powerful project management and team collaboration platform that helps organizations manage their work, track projects, and achieve their goals. It provides a comprehensive suite of tools for task management, project tracking, team coordination, and workflow optimization.

​
Configuring Asana as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Asana option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need OAuth credentials to connect to Asana. You’ll need to provide:
  • Authorization: Log in with your Asana account and grant permissions for Nekt to access your workspace data.
  • Workspace ID: The ID of your Asana workspace. You can get it from the Admin URL (https://app.asana.com/admin/), it’s the number that appears right next to https://app.asana.com/admin/. Alternatively, if you’re logged in with your account, you can click this link and simply copy the gid value.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you. The available streams include projects, tasks, teams, portfolios, and more.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Asana and their corresponding fields:
Stream for managing projects in your Asana workspace.Key fields:
Stream for managing tasks within projects.Key fields:
Stream for managing subtasks within tasks.Key fields:
Stream for managing teams in your workspace.Key fields:
Stream for managing users in your workspace.Key fields:
Stream for managing tags used to categorize tasks.Key fields:
Stream for tracking activity and comments on tasks.Key fields:
Stream for managing custom fields in your workspace.Key fields:
Stream for managing portfolios that group related projects.Key fields:
Stream for managing items within portfolios.Key fields:
Stream for managing custom fields specific to portfolios.Key fields:
Stream for managing custom fields specific to projects.Key fields:
Stream for tracking project status updates.Key fields:
Stream for tracking time entries on tasks.Key fields:
Stream for managing resource allocations.Key fields:
Stream for managing organizational goals.Key fields:

​
Implementation Notes

​
Pagination and Sync Behavior

  • Project Stream Pagination: The connector fetches all pages of the Projects stream upfront before syncing any nested child streams (such as Tasks, Subtasks, Stories, etc.). In Asana workspaces with large amounts of nested data, syncing children inline can cause the Asana pagination token to expire, failing the sync with a 400 "pagination token has expired" error. Consuming the pagination fully in advance keeps API requests close together and prevents this expiration, ensuring data extraction reliability.

​
Skills for agents

Download Asana skills file

Asana connector documentation as plain markdown, for use in AI agent contexts.