Reference · Credentials

Asana API credentials

Used by 2 BusyBot nodes.

Type asanaApi 1 field

The Asana credential holds a personal access token generated from your Asana account. The token acts as you, so it sees exactly the workspaces, projects and tasks your own account can see — and activity it creates appears under your name.

Fields

FieldTypeRequiredNotes
Access Token
accessToken
password Yes Your Asana Personal Access Token.

Getting your credentials

  1. Sign in to Asana and open the developer console.
  2. Create a new personal access token, naming it for where it will be used.
  3. Copy the token immediately — it is shown only once.
  4. Paste it into the credential’s Access Token field in BusyBot.

Permissions and scopes

A personal access token inherits your own permissions. Anything you cannot see, the automation cannot see either — and anything you can change, it can change. For shared automation, consider generating the token from a dedicated service account with access limited to the relevant projects.

Troubleshooting

  • 401 Unauthorized — the token is wrong or was revoked. Generate a new one in the developer console.
  • 404 on a task or project — the account behind the token does not have access to it, or the GID is wrong.
  • Changes attributed to the wrong person — the token acts as its creator, so activity shows under that account. Use a dedicated account if attribution matters.

Frequently asked questions

Who do actions appear as in Asana?

The account that created the token. If you would rather automation activity not appear under your own name, generate the token from a dedicated service account.

Does the token expire?

Personal access tokens remain valid until revoked, so treat the value with the same care as a password.

Why can the workflow not see a project?

Because the token's account cannot see it. Grant that account access to the project in Asana.

Does one token cover the Asana node and its trigger?

Yes, both declare the same credential type.

Nodes that use Asana API

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.