Asana
Find, create and update Asana tasks and projects from agent work.
Connect it with: Sign in (OAuth), API key. Asana's own documentation: https://developers.asana.com/docs/oauth.
What agents can do
Connect Asana so the agents working your tasks can reach it. With it connected, they can:
- Find the Asana task a Jaah task names and read its description, custom fields, subtasks and comments.
- Create a follow-up task in the right project when an agent finds more work.
- Post a comment with progress or a pull request link on the task being worked.
- Mark a task complete or move it to another section when the work is done, if you granted write access.
Before you start
- An Asana account that is a member of the workspaces and projects agents should reach.
- On a workspace that restricts third-party apps, an Asana admin must allow Jaah (Admin console > Apps).
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Asana
This is the quickest way in: you sign in to Asana and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for Asana and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect Asana. Asana's sign-in window opens.
- Sign in to Asana if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at Asana yet. Use an API key, or your own OAuth app, until it does.
Scopes Jaah requests
Jaah asks Asana for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
| Scope | Why Jaah asks for it | Required |
|---|---|---|
users:read | Read your profile, so the connection shows whose it is | Yes |
workspaces:read | List your workspaces, so agents know where to look | Yes |
teams:read | List teams, to find a team's projects | Yes |
projects:read | Read projects and their sections | Yes |
tasks:read | Read tasks, their fields and subtasks | Yes |
stories:read | Read task comments and history for context | Yes |
tasks:write | Create tasks, update fields and complete tasks when a task reports back | No — you may untick it |
stories:write | Comment on tasks with progress and results | No — you may untick it |
Connect with an API key
Prefer this when you cannot sign in with Asana — for example a service account, or a token your admin issued. On the Connect screen select Use an API key instead.
Find each value first:
- Personal access token: Asana > your profile photo > My settings > Apps > View developer console (app.asana.com/0/my-apps) > Create new token: give it a description such as Jaah, accept the terms, then copy the token - Asana shows it once.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Asana card.
- Name the secret and choose who can use it.
- Select Use an API key instead.
- Fill in Personal access token.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Register your own OAuth app at Asana when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in Asana's developer console, https://app.asana.com/0/my-apps (Asana's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new Asana secret, select Use your own OAuth app, paste both values and select Connect Asana.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah calls Asana's API once (GET https://app.asana.com/api/1.0/users/me?opt_fields=name,email) with the stored values, and shows who it answered as, or which value Asana refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
A key connection hands the agent its fields: api_key.
Tell the agent in your task description which secret to use, for example “use the Asana secret org/asana”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Asana once the test passes. Steps: Replace or delete a secret.
- Reconnect: when Asana ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Asana's side too, revoke Jaah in Asana's settings, or revoke or delete the key at Asana.
Limitations
- Agents act as the connected Asana user: they see only what that user can see, and their changes show under that user's name.
- Agents cannot manage workspace members, admin settings, billing or portfolios' permissions.
- Asana rate-limits each user to about 150 requests a minute on free plans and 1,500 on paid ones.
- Agents can do only what the connected Asana account and its granted scopes allow.
Troubleshooting
Test says Asana rejected the personal access token (401)
The token was deauthorized or mistyped. Create a new one in the developer console and select Replace on the secret.
Consent fails with a forbidden_scopes or invalid_scope error
Jaah's app at Asana is missing one of the scopes listed above. An operator adds it on the app's OAuth tab; with your own app, add it to yours.
Agents get 403 Forbidden on a project
The connected user is not a member of that project or its team. Add the user in Asana, or connect an account that is.
The secret shows Needs reconnect
Asana revoked the grant, for example after the user removed Jaah under My settings > Apps. Select Reconnect.
Still stuck? Select Test and read the result: it names the value Asana refused and the status it answered.
FAQ
Can I limit agents to read-only?
Yes. Untick tasks:write and stories:write on the Connect screen, or use a token of a user who has comment-only access to the projects.
Does connecting cost an Asana seat?
No. Jaah uses the connected user's own seat.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Asana account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.