Asana

Pro and above. Setup is a personal access token and a project id.

Connect

Create a personal access token

Go to the Asana developer console → Create new token. Name it "Annot8" and copy the value — it's shown once.

Find the project id

Open the Asana project. The id is the long number in the URL:

https://app.asana.com/0/1234567890123456/list
                        └────────────────┘

Connect in Annot8

Integrations in the sidebar → Asana → enter the token and project id → Connect, then Test.

Enable it per project

Project → Integrations → toggle Asana on.

What gets created

Every new thread on an enabled project creates an Asana task named [Feedback] <comment>, with the author, the comment, and a link to the page in the notes.

This fires on every thread. Point it at a dedicated intake project, and use Asana rules to triage from there into your real boards.

The token acts as the account that created it, so tasks show that account as the creator and the token inherits its access. Use a service account for a team setup rather than a token belonging to someone who may leave.

Different Asana projects per Annot8 project

Asana doesn't support per-project overrides — the workspace connection posts to one intake project. Under Project → Integrations you can turn Asana off for projects that shouldn't post there, and Asana's own automation can route tasks onward from the intake project.

Practical advice

Asana rules pair well with this: let Annot8 drop every task into one intake project, then use Asana's own automation to assign, tag, and move them. That keeps the routing logic in the tool your team already lives in.

Troubleshooting

401. The token was revoked or pasted with whitespace.

403 or 404. The token's account can't see that project. Asana returns 404 for projects a token has no access to, so this often means permissions rather than a wrong id.

Wrong id. Grabbing the number from a task URL rather than a project URL is the usual mistake. The project id is the segment immediately after /0/.