Skip to main content
Telara

Integrations / Asana

Asana logo

Asana

Asana is a work management platform where teams can stay connected and organized

OAuth 2.0
Indexes
Actions
Events

What Telara does

Capability matrix

Before you connect

Prerequisites

An Asana workspace or organization.
A full member who can authorize apps. Guests cannot grant workspace-wide access. Org-wide install needs an admin.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → Asana. Telara sends you to asana.com. You do not create an Asana OAuth app.
2
Approve and pick the workspace
On Asana’s Grant permission screen, review the access, then click Allow. If you belong to several workspaces, pick the one Telara should use — Asana users often have a personal workspace plus a company one.

Permissions Telara requests

  • attachments:read
    OAuth 2.0
  • attachments:write
    OAuth 2.0
  • custom_fields:read
    OAuth 2.0
  • goals:read
    OAuth 2.0
  • openid
    OAuth 2.0
  • email
    OAuth 2.0
  • portfolios:read
    OAuth 2.0
  • project_templates:read
    OAuth 2.0
  • projects:read
    OAuth 2.0
  • projects:write
    OAuth 2.0
  • projects:delete
    OAuth 2.0
  • stories:read
    OAuth 2.0
  • stories:write
    OAuth 2.0
  • tags:read
    OAuth 2.0
  • task_custom_types:read
    OAuth 2.0
  • task_templates:read
    OAuth 2.0
  • tasks:read
    OAuth 2.0
  • tasks:write
    OAuth 2.0
  • tasks:delete
    OAuth 2.0
  • team_memberships:read
    OAuth 2.0
  • teams:read
    OAuth 2.0
  • time_tracking_entries:read
    OAuth 2.0
  • users:read
    OAuth 2.0
  • workspaces:read
    OAuth 2.0
  • tags:write
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for
  • Expires At
Bearer token

Personal Access Token (PAT) for Asana

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for
  • Access token

Knowledge

What gets indexed

ResourceCoverage
WorkspacePartial — not every record the vendor holds is synced
ProjectsPartial — not every record the vendor holds is synced
TaskPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
WorkspaceUp to 1 dayRemoved records disappear on the next full sync
ProjectsUp to 1 dayprovider tombstone
TaskUp to 1 dayprovider tombstone

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Workspace, Projects, Task.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Guest accounts see a thin slice. Use a full member if you want team-wide work.
[object Object]