What does the Asana data include?

6 tables: projects (one row per project), tasks (one row per task), workspaces (one row per workspace), tags (one row per tag), teams (one row per team) and users (one row per user).

Do I need an account with Asana?

Yes. You connect your own Asana account once, from Ingest, and the data comes from what that account can see.

How fresh is the data?

As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.

Will running it again create duplicate rows?

No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.

Do I need to write code?

No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Asana

Productivity

Ready to use

Work management data from Asana: the projects, tasks, teams and tags in your organization's workspaces. Ingest delivers this data to a data warehouse you own as 6 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What people use it for

See every project and task in one placeCombine all your Asana workspaces, projects and tasks into one report.
See who is in each workspaceList the people and teams working in each Asana workspace.
Track tags across projectsSee which tags are used, and where, across all your projects.

What you get

Table	Each row is
Projects `projects`	One project
Tasks `projects_tasks`	One task
Workspaces `workspaces`	One workspace
Tags `workspaces_tags`	One tag
Teams `workspaces_teams`	One team
Users `workspaces_users`	One user

Good to know

Projects: Each run reads the projects in every workspace again, so changes show up after the next run.
Tasks: Each run reads the tasks in every project again, so changes show up after the next run.
Workspaces: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.
Tags: Each run reads the tags in every workspace again, so changes show up after the next run.
Teams: Each run reads the teams in every workspace again, so changes show up after the next run.
Users: Each run reads the users in every workspace again, so changes show up after the next run.

How it works

Choose Asana. Connect your Asana account once, from Ingest.
Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
Pick a schedule. Daily is the default, and weekly and monthly are there too.
Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

What does the Asana data include?: 6 tables: projects (one row per project), tasks (one row per task), workspaces (one row per workspace), tags (one row per tag), teams (one row per team) and users (one row per user).
Do I need an account with Asana?: Yes. You connect your own Asana account once, from Ingest, and the data comes from what that account can see.
Which warehouses can Asana data go to?: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?: As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?: No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
Do I need to write code?: No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

For your data team: technical reference

Connector asana, version 0.1.0, a REST source, status beta, authentication oauth2.

Vendor documentation: https://developers.asana.com/docs

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`projects` Projects in each workspace (transformer child of workspaces). Anchored on the workspace rather than on the root /projects collection, which answers 200 to a bare request but 400 ("Need to specify a workspace to paginate!") the moment a limit is present. A collection that cannot be paginated can only ever return its first page, so the root form is unusable for any real account and is not used here.	beta	parent_child	merge	`gid`	-
`projects_tasks` Tasks in each project (transformer child of projects).	beta	parent_child	merge	`gid`	-
`workspaces` All workspaces and organizations the credential can see. This is the anchor of the connector. Every other resource hangs off it, so nothing here asks the customer to look up and paste a workspace id.	beta	full	merge	`gid`	-
`workspaces_tags` Tags in each workspace (transformer child of workspaces).	beta	parent_child	merge	`gid`	-
`workspaces_teams` Teams in each workspace (transformer child of workspaces).	beta	parent_child	merge	`gid`	-
`workspaces_users` Users in each workspace (transformer child of workspaces).	beta	parent_child	merge	`gid`	-

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Jira, Salesforce, Airtable, Clockify, Facebook Ads, Frankfurter.

Get Asana data into your warehouse

Last updated 2026-10-16.