Asana support

Last updated date:

Install, authorize, reconnect, and troubleshoot Asana without sharing tokens or customer content.

1. Before you start

  • Choose the Seedling workspace that should own the connection and confirm you are a current administrator of it.
  • Find the immutable Asana workspace GID by signing in to Asana and opening https://app.asana.com/api/1.0/workspaces.
  • Use an Asana account with native access to every project and task the connection should synchronize.
  • Do not send PATs, OAuth tokens, customer task text, or attachment contents through email or ordinary support tickets.

2. Connect the Seedling-managed app

If Asana says the app is unavailable, the OAuth app has not yet been distributed to that workspace. During pre-publication testing, an Asana app owner must add the test workspace under Manage distribution.

  1. In Seedling, open Apps or Connections in the intended workspace and select Asana.
  2. Review the Asana data-use notice, enter the intended Asana workspace GID, and continue to Asana.
  3. Approve the displayed granular read-only scopes.
  4. Return to Seedling and confirm that Asana shows as connected.
  5. Allow the initial bounded synchronization to complete before evaluating coverage.

3. Connect a customer-managed PAT

PAT access changes whenever the token owner’s native Asana permissions change. Rotate the PAT through the same form; Seedling rejects credentials for a different Asana workspace.

  1. Create an Asana personal access token from an account that can read the intended workspace.
  2. In Seedling, choose Use a personal access token.
  3. Enter the PAT and the exact workspace GID. Seedling rejects a GID the token cannot read and always calls the public Asana API.
  4. Connect and confirm the verified Asana workspace.

4. Authorization problems

Missing scopes
Confirm all eight displayed read scopes are enabled in the Asana developer console, then restart authorization. Seedling rejects partial grants.
Workspace mismatch
Confirm the GID identifies a workspace visible to the authorizing Asana user and matches the already connected account during reauthorization.
Account conflict
One Asana workspace can route to only one Seedling workspace per environment. Contact support with workspace names and GIDs, never credentials.
Authorization required
If refresh is rejected, Seedling stops synchronization and asks a workspace admin to reconnect the same credential mode.

5. Missing or delayed data

  1. Confirm the connection is active and the authorizing Asana user can open the missing object.
  2. For OAuth, remember that workspace and project membership staging is intentionally unavailable; Seedling does not request Full Permissions.
  3. Check whether private projects, guests, removed users, archived projects, or native Asana access explain the difference.
  4. Allow provider rate-limit retries and periodic reconciliation to complete.
  5. If the issue remains, contact support@tryseedling.ai with safe timestamps, the Seedling workspace, Asana workspace GID, and affected object GIDs. Do not include task text, tokens, or attachment contents.