Skip to main content

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:

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:

  1. Create a new service account and name it Glean Service Account or something similar using the instructions given in the Asana service account documentation.
  2. Make sure to select Full permissions when creating the service account to allow access to all data.
  3. Copy the access token listed.

For other Asana account types:

  1. Create a new Asana administrator account called Glean or something similar.
  2. Create a new personal access token for the Glean administrator using the instructions at this Personal access tokens documentation.
  3. Copy the personal access token listed.

Step 2: Determine your domain name

  1. While logged in to the admin account, visit this URL to find out the workspace name.
  2. Copy the domain name. Note that the domain name is case sensitive.

Step 3: Add the Asana connector in Glean

  1. In the Glean, go to the Admin Console, navigate to Connectors and select Add Connector.
  2. Choose Asana from the available connectors. If you cannot see this option, contact Glean support to enable it.
  3. Enter the Name, Access token and Asana Domain Name (Workspace Name).
  4. Click Save.

Step 4: Schedule the first crawl

  1. Start the integration and monitor the initial crawl and webhook configuration.

Step 5: Validate the crawl and permissions

  1. After the crawl completes, verify that Asana documents and tasks appear in Glean search.

See also