Asana setup
This page describes how to install and configure the Asana connector. Setup takes place in both Asana and the Glean Admin Console.
To set up the Asana connector:
- Confirm the requirements and prerequisites.
- Generate an access token in Asana.
- Determine your Asana domain name.
- Add the connector in Glean and start the first crawl.
Requirements
To set up and operate the Asana connector, ensure that both technical and credentials requirements are met.
Technical requirements
- Glean platform instance.
- Access to your company’s Cloud Provider account.
- Supported Asana plan. Enterprise edition is required for certain features and administrators must enable service accounts.
- Web connectivity between Glean and Asana’s API endpoints.
Credential requirements
- For Asana Enterprise accounts: You must generate a service account and provide full permissions, then obtain the associated access token.
- For other Asana account types: Create a dedicated Asana administrator user, the recommended name is Glean, then generate a personal access token for this user.
- The Asana domain is case-sensitive and must match your workspace configuration.
Permission requirements
- Service accounts or admin tokens require full access permissions. Glean uses these to ensure comprehensive crawl and prevent interruptions due to future Asana product changes.
- The required scopes for API tokens are those that permit read access to projects, tasks, users, teams, organizations, workspaces, and activity/events.
- For successful incremental crawling, the token must have permission to receive webhook events.
Prerequisites
- Confirm you have Glean workspace admin rights.
- Confirm you have Asana admin or service account credentials with required scopes.
- Determine Asana workspace domain name (case-sensitive).
- Optionally, prepare a list of projects to redlist.
Configuring the Asana connector is typically performed within the Admin Console. Many setup fields are pre-populated, with step-by-step validation on save.
Step 1: Generate an access token
For Asana Enterprise accounts:
- Create a new service account and name it Glean Service Account or something similar using the instructions given in the Asana service account documentation.
- Make sure to select Full permissions when creating the service account to allow access to all data.
- Copy the access token listed.
For other Asana account types:
- Create a new Asana administrator account called Glean or something similar.
- Create a new personal access token for the Glean administrator using the instructions at this Personal access tokens documentation.
- Copy the personal access token listed.
Step 2: Determine your domain name
- While logged in to the admin account, visit this URL to find out the workspace name.
- Copy the domain name. Note that the domain name is case sensitive.
Step 3: Add the Asana connector in Glean
- In the Glean, go to the Admin Console, navigate to Connectors and select Add Connector.
- Choose Asana from the available connectors. If you cannot see this option, contact Glean support to enable it.
- Enter the Name, Access token and Asana Domain Name (Workspace Name).
- Click Save.
Step 4: Schedule the first crawl
- Start the integration and monitor the initial crawl and webhook configuration.
Step 5: Validate the crawl and permissions
- After the crawl completes, verify that Asana documents and tasks appear in Glean search.