Asana
Read and write Asana work - browse workspaces, projects and board sections, list and search tasks, create, update and delete them, and work their comment threads.
Connect an Asana account with a personal access token to run its work end to end: list the workspaces and projects the token can reach, read a project's board sections, page through a project's or a person's tasks, search a workspace on paid plans, create tasks and subtasks with assignees, dates, tags and custom field values, update or complete them, delete them to the trash, and read and post task comments. Everything written through this connection is attributed in Asana to the person whose token it is.
Connect
| Credential field | Required | Where it comes from |
|---|---|---|
Personal access token (PERSONAL_ACCESS_TOKEN) | Yes | From My settings → Apps → Manage developer apps → Personal access tokens. It carries the full access of the user who created it - there are no scopes to narrow it - and every write is attributed to them. |
Tools
| Tool | Access | What it does |
|---|---|---|
Whoami (yekar.asana.whoami) | Read | The Asana user this connection's token belongs to, and the workspaces they can reach. Run it first - every other tool is scoped to this person's own access, and their workspace gids are what the other tools ask for. |
List workspaces (yekar.asana.list-workspaces) | Read | The workspaces and organizations this token's user belongs to. A workspace gid is what Search tasks and the assignee filter on List tasks require - everything else in Asana hangs off one of these. |
List projects (yekar.asana.list-projects) | Read | A page of projects in a workspace or team. Archived projects are hidden unless you ask for them. This endpoint reports no total; counting projects means paging through them all. |
Get project (yekar.asana.get-project) | Read | One project in full - its notes, owner, team, dates, and its current status update. Use List projects to find the gid. |
List project sections (yekar.asana.list-project-sections) | Read | The sections of a project - the columns of its board view, in board order. Their gids are what Create task and List tasks use to place or read a specific column. |
List tasks (yekar.asana.list-tasks) | Read | A page of tasks from ONE scope - a project, a board section, a tag, or a person's assigned work in a workspace. Asana cannot list every task at once. This endpoint reports no total; counting means paging through them all. |
Get task (yekar.asana.get-task) | Read | One task in full - notes, assignee, dates, tags, followers, custom field values, and which section of which project it sits in. Custom fields come back as their rendered display values. |
Search tasks (yekar.asana.search-tasks) | Read | Search a workspace's tasks by text and filters. PAID PLANS ONLY - Asana answers Payment Required on Free. Results cannot be paged and Asana documents them as approximate, so use List tasks when completeness matters. |
Create task (yekar.asana.create-task) | Write | Create a task in a project (or bare in a workspace), optionally as a subtask. Asana has no dry run: the task exists as soon as this returns, and it will appear in every view its project feeds. |
Update task (yekar.asana.update-task) | Write | Change a task's fields - rename it, rewrite its notes, complete or reopen it, reassign it, move its dates, or set custom field values. Only the fields you pass are touched; pass null to CLEAR assignee or a date. |
Delete task (yekar.asana.delete-task) | Write | Delete a task. It moves to the token owner's trash - recoverable by hand for 30 days, then gone - and takes its subtasks with it. There is no API to undo this. |
List task comments (yekar.asana.list-task-comments) | Read | A page of the comments people have left on a task, newest last. Asana stores comments in the same feed as its own activity records; this returns only what humans wrote unless you ask for the rest. |
Add task comment (yekar.asana.add-task-comment) | Write | Post a comment on a task, attributed to the person whose token this connection holds. Every follower of the task is notified immediately - there is no draft state and no way to unsend. |
Notes
- Create a token in Asana under My settings → Apps → Manage developer apps → Personal access tokens, and paste it here. Asana shows it once.
- A personal access token IS that person: it carries exactly their access, no more, and every task, edit and comment made through this connection appears in Asana under their name. Bind automations using this integration as service connections so the attribution is a role rather than an individual's side effect.
- There is no scope picker on an Asana token - unlike most integrations, you cannot narrow what it may do. The only ceiling is the access of the user who created it, so create it from an account whose reach matches what the automation should be able to touch.
- Run Whoami first: it reports the workspace gids every other tool asks for, and confirms which person the token is.
- Asana identifies everything by a
gid, a string of digits you can read off the end of a resource's URL in Asana. Names are never accepted where a gid is asked for. - Search tasks needs a PAID Asana plan - on Free it fails with Payment Required, which no permission change can fix. List tasks on a project works on every plan and is the exhaustive option regardless.
- Rate limits are per minute and per domain: 150 requests on Free, 1,500 on paid plans, with a tighter budget on search.
- Add one credential per token - a production and a sandbox token can live on the same connection.