Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Asana from the Previews page. See Manage Azure Databricks previews.
Find answers about the plans, tables, historical data, data access, and authentication methods of the managed Asana connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which Asana plans does the connector require?
The connector works with any Asana plan. Some tables depend on plan features. Portfolios, goals, and time tracking require an Advanced or Enterprise plan, and custom fields require a Starter plan or higher. See Asana pricing.
Which tables does the connector support?
The connector supports tables for workspaces, users, teams, projects, sections, tasks, stories, tags, custom fields, attachments, portfolios, goals, status updates, memberships, and time tracking entries. For the full list and schemas, see Supported source tables.
How far back can the connector ingest data?
All tables are full refresh. Each pipeline update ingests all records that the authorizing user can access in Asana at the time of the update.
Which data can the connector access?
The connector reads Asana data as the user who authorized the connection. It ingests only the objects that this user can view in Asana. See Asana OAuth.
Which authentication methods does the connector support?
The connector supports OAuth user-to-machine (U2M) authentication through an Asana OAuth app only. OAuth machine-to-machine (M2M) authentication, personal access tokens, and basic authentication aren't supported.