An Asana connection lets workflows create, update, complete and find tasks, comment, attach files and create projects — and start a run the moment a task is added, completed, changed or commented on. It connects with a personal access token that you make in Asana. Everything the steps do is done as the person who made the token.

Who can do this

  • In Bizomate: workspace Admins and Editors, on every plan — Asana is not a premium connection. Viewers see the connection but cannot add or change it.
  • In Asana: anyone can make a token for their own account. It reaches every workspace and project that account can.

Steps

In Asana, make the token:

  1. Sign in to Asana. Select your profile photo at the top right, then My settings.
  2. Open the Apps tab and select View developer console.
  3. Under Personal access tokens, select Create new token.
  4. In Token name, type Bizomate, agree to Asana's API terms, and select Create token.
  5. Copy the token. Asana shows it only once.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Productivity, select Asana. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace Asana.
  4. Paste the token in Personal access token — placeholder 2/1208…. In Asana: your profile photo › My settings › Apps › View developer console › Personal access tokens › Create new token. It acts as you, in every workspace you are in.
  5. Leave Test the connection before saving ticked. Bizomate asks Asana whose token it is before keeping it.
  6. Select Save connection. The button reads Testing while Asana is asked.

The toast "Connection added" says what Asana answered — for example "“Consulace Asana” is ready. Reached Rohan Mehta · Asana workspace Consulace."

What happens next

  • The connection appears under Productivity. Its panel shows Replace token, Test and Revoke — never the token. Stored encrypted. Secret fields are never shown again after you save.
  • Test answers with the account's name and its Asana workspaces — Reached Rohan Mehta · Asana workspace Consulace, or Reached Rohan Mehta · 2 Asana workspaces for an account in more than one.
  • Asana steps and triggers list it under Connection. Their Workspace list marks each one Organisation or Workspace, and the Project list shows each project's team.

Good to know

  • The token does not expire. It stops working if you delete it in the developer console, or the account leaves the Asana organisation.
  • Tasks made by a workflow show the token's owner as their creator. Some teams make a separate Asana account for automation, so it is clear what a workflow did.
  • To replace the token, open the connection's panel, select Replace token, paste the new token and select Replace token. The old one is used until then. The toast "Token replaced" says "Workflows that use “Consulace Asana” use the new key from their next run."
  • Signing in with Asana instead of a token is not offered yet; the token is the only way to connect.

If something goes wrong

What you see Why What to do
Asana refused it — "Asana refused: Not Authorized. Check the connection's details on Connections. Nothing was saved." The token was mistyped or deleted. Make a new token and paste it.
"Fill in Personal access token." The box is empty. Paste the token.
Nothing to pick — "The token reaches no workspace. Make it while signed in to the Asana account its workflows use, then Refresh." The token belongs to an account in no workspace. Make the token from the right Asana account.
Nothing to pick — "This workspace has no projects you can see. Make one in Asana, or join one, then Refresh." The account is in no project of that workspace. Choose the right Workspace, or ask to be added to the project.
"Could not reach Asana: …" or "Asana did not answer within 30 seconds." Asana could not be reached. Try again in a few minutes.