Asana

Asana is a project management platform that helps teams organize tasks, track projects, and coordinate work. With Coupler.io, you can automatically export your Asana data — tasks, projects, users, and more — to spreadsheets, databases, or BI tools without writing a single line of code.

Why connect Asana to Coupler.io?

• Centralize project data — pull tasks, sections, stories, and portfolios into one place for reporting

• Track team performance — combine Users and Tasks data to see workload distribution across your team

• Build live dashboards — send Asana data to Google Sheets, Looker Studio, BigQuery, or AI tools like ChatGPT or Gemini

• Keep data fresh automatically — schedule recurring exports so your reports always reflect the latest project status

Prerequisites

• An active Asana account (Free, Premium, Business, or Enterprise)

• Your Asana account must belong to an organization or team workspace — personal project spaces do not support API access

• You must have access to the projects, portfolios, or workspaces you want to export

Asana's API does not work with personal project spaces. If you see a "Data cannot be fetched" error, make sure your account is part of an organization workspace, not a personal one.

Quick start

Start with the Tasks entity — it contains the richest data and is the most commonly used for reporting and analysis.

1

Create a new data flow in Coupler.io. Go to your Coupler.io account and click Add data flow. Search for and select Asana as your source.

2

Connect your Asana account via OAuth. Click Connect and sign in to Asana when prompted. Coupler.io uses OAuth, so no API keys are needed — just authorize access and you're in.

3

Select an entity to export. Choose the data entity you want — Tasks, Projects, Users, Portfolios, and more. See the table below for all available entities.

4

Choose your destination. Select where you want to send your data — Google Sheets, Excel, BigQuery, Looker Studio, PostgreSQL, or an AI destination like ChatGPT, Claude, or Gemini.

5

Run your data flow. Click Run to execute a manual run. Once it completes successfully, your Asana data will appear in your chosen destination.

Asana data overview

Coupler.io gives you access to 9 Asana entities, covering everything from individual tasks and comments to top-level portfolios and workspaces. This page explains what data is available and how to use it effectively.

Available entities

Entity	Best used for
Tasks	Task tracking, workload analysis, deadline monitoring
Projects	Project status reporting, portfolio views
Sections	Workflow stage analysis
Stories	Audit trails, comment history, activity tracking
Tags	Categorization and filtering across tasks
Teams	Org structure, team-level reporting
Users	Capacity planning, user access audits
Portfolios	Executive-level project tracking (Business/Enterprise plans)
Workspaces	Multi-workspace inventory

Tasks

Key fields

Field	Description
name	Task title
assignee.name	Name of the person assigned
due_on	Due date
completed	Whether the task is complete (true/false)
completed_at	Timestamp when the task was marked complete
created_at	When the task was created
modified_at	When the task was last updated
projects	Projects the task belongs to
tags	Tags applied to the task
parent	Parent task (for subtasks)
custom_fields	Custom fields added in Asana (returned as JSON)

Custom fields are returned in a JSON-formatted column. You can use Coupler.io's calculated column feature with json_extract to pull specific custom field values into their own columns.

Projects

Key fields

Field	Description
name	Project name
owner.name	Project owner
current_status.text	Latest project status update
due_date	Project due date
team.name	Team the project belongs to
created_at	When the project was created
modified_at	Last modified date

Users

Key fields

Field	Description
name	Full name
email	User email address
workspaces	Workspaces the user belongs to

Stories

Key fields

Field	Description
created_at	When the story was created
created_by.name	Who created the story
text	Content of the comment or activity entry
type	Story type (comment, system)
resource_subtype	Specific activity type (e.g., assigned, completed)

Common field combinations

• Tasks + Users — Join on assignee.gid to build workload and capacity reports

• Tasks + Projects — Join on project ID to filter or group tasks by project

• Projects + Teams — Join on team.gid to see project counts and status per team

• Stories + Tasks — Join on task ID to attach comment history to task records

Use Coupler.io's Join transformation to combine any two of these entities in a single data flow.

Use cases by role

Project managers

• Export Tasks filtered by modified_at to track what changed this week

• Build a project health dashboard in Looker Studio using Projects data

• Monitor overdue tasks by filtering on due_on and completed = false

• Use Sections data to visualize workflow stage distribution

Team leads

• Join Tasks and Users to see per-person task counts and completion rates

• Export Stories to review activity history and identify bottlenecks

• Send task data to ChatGPT or Claude to generate automated team summaries

Operations & reporting

• Use Portfolios to get a cross-project view for executive dashboards

• Append Tasks data from multiple Asana workspaces using Coupler.io's Append transformation

• Export to BigQuery or PostgreSQL for long-term trend analysis

• Use the Changed after filter to do incremental loads and keep data warehouse tables up to date

Platform-specific notes

• Personal project spaces do not support Asana's API — you must be part of an organization workspace

• Portfolios are only available on Asana Business and Enterprise plans

• Filtering tasks by a specific project GID is not natively supported — export all Tasks and filter in your destination or using Coupler.io's filter transformation

• Subtasks are returned as Tasks with a non-null parent field — they are not a separate entity

• Attachments and media files cannot be exported — only structured data is available

• The Changed after filter applies to the entity's modified_at field, so it works well for incremental exports of large task lists

Asana common issues

Connection issues

OAuth authorization fails or I'm redirected back with an error

Make sure you're signing in with the correct Asana account — the one that has access to the workspace you want to export. Try disconnecting the existing connection in Coupler.io, revoking Coupler.io's access in your Asana account settings, and reconnecting from scratch.

Coupler.io doesn't show my Asana Business account or workspace

If your workspace isn't appearing, check that your Asana account role allows Portfolio or workspace access. For Portfolios specifically, confirm you have create/edit permissions in Asana. If the issue persists, try re-authorizing your connection — sometimes a fresh OAuth handshake resolves visibility problems.

Missing data

Custom fields are missing or show as a long JSON string

Asana returns custom fields as a JSON-formatted column rather than individual columns. The data is there — it's just nested. Use Coupler.io's calculated column feature with the json_extract function to pull specific custom field values into their own columns.

Some columns are empty (e.g., completed_by.name)

Certain fields like completed_by.name are only populated when a task is marked complete by a specific user — they'll be empty for tasks completed via automation or bulk actions. This is a limitation of the data Asana's API returns, not a Coupler.io issue.

I can't filter tasks by a specific project

Filtering Tasks by a specific project GID is not currently supported as a source parameter. As a workaround, export all Tasks and use Coupler.io's filter transformation — or filter in your destination (e.g., Google Sheets filter views or BigQuery WHERE clauses) using the projects column.

Subtasks are not appearing in my Tasks export

Subtasks are included in the Tasks entity but are identified by a non-null parent field. If you're not seeing them, check whether you're filtering out rows with a parent value. There is no separate subtasks entity.

Permission errors

"Data cannot be fetched" error when running the data flow

This error most commonly occurs when your Asana account is using a personal project space instead of an organization workspace. Asana's API does not support personal spaces. You'll need to migrate your projects to an organization workspace to use Coupler.io. Contact Asana support for help with migration.

This is the most common error reported for Asana. Personal project spaces are not compatible with Asana's API — there is no workaround other than migrating to an organization workspace.

Portfolios entity returns no data

Portfolios are only available on Asana Business and Enterprise plans. If you're on a Free or Premium plan, this entity will return empty results. Also verify that you have permission to view portfolios in your workspace.

Data discrepancies

Task count in Coupler.io doesn't match what I see in Asana

Coupler.io fetches tasks across all workspaces your account has access to. If you're seeing more tasks than expected, you may be pulling from multiple workspaces. Use the Changed after date filter to scope your export, and filter by the projects column to narrow results after import.

Rate limits

Data flow times out or fails on large workspaces

Asana's API can slow down when responding to requests for very large workspaces (hundreds of projects, thousands of tasks). If your data flow consistently times out, use the Changed after date filter to export only recently modified records. Running incremental exports rather than full refreshes significantly reduces API response time.

Asana FAQ

Can I filter Tasks by a specific project?

Not at the source level — Coupler.io fetches all tasks your account has access to. Once the data is in your destination, filter using the projects column. In Google Sheets, use a filter view or QUERY formula. In BigQuery or SQL destinations, use a WHERE clause. Alternatively, use Coupler.io's built-in filter transformation after the source step.

Why do I get a "Data cannot be fetched" error?

This almost always means your Asana account is using a personal project space, which Asana's API does not support. To fix it, migrate your data to an organization workspace in Asana. You can reach out to Asana support for help with the migration process.

Are custom fields from Asana included in the export?

Yes — custom fields are included in the Tasks export, but they're returned as a JSON-formatted column rather than individual columns. Use Coupler.io's calculated column feature with the json_extract function to extract specific custom field values into their own columns.

Can I export subtasks?

Subtasks are part of the Tasks entity. They appear as regular task rows but have a non-null parent field that references the parent task. Filter on parent to separate top-level tasks from subtasks in your destination.

Can I export attachments or media files from Asana?

No — Coupler.io only exports structured data from Asana (text fields, dates, statuses, IDs, etc.). Attachments, images, and other media cannot be exported.

Why is the Portfolios entity empty?

Portfolios are only available on Asana Business and Enterprise plans. If you're on a Free or Premium plan, this entity will return no data. Also check that your account has view access to portfolios in your workspace.

Can I combine data from multiple Asana workspaces?

Yes. Add each workspace connection as a separate source in your data flow and use the Append transformation to merge them into one dataset. This is useful if your organization runs multiple Asana workspaces for different teams or clients.

Can I send Asana data to an AI tool like ChatGPT or Gemini?

Yes — Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can send your Tasks or Projects data directly to these tools for summarization, analysis, or automated reporting.

My data flow keeps timing out on large exports. What should I do?

Use the Changed after date filter to limit the export to recently modified records. This is the most effective way to avoid timeouts on large Asana workspaces. For ongoing reporting, set up incremental exports (run daily, filter by the past day or week) rather than full refreshes.

Can I write data back from Coupler.io to Asana?

No — Coupler.io is a one-way data pipeline. It reads data from Asana and sends it to your destination. Writing data back to Asana is not supported.

For a full list of available fields per entity, see Data Overview. For setup tips and how to handle large workspaces, see Best Practices. If you're hitting errors, check Common Issues.