How to connect Asana to Hermes Agent
Connect Asana to Hermes with ClawLink in one click — 247 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.

Track tasks, projects, and workflows. Once connected, Hermes Agent can read and act on Asana from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Asana access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Asana setup: pair once in the browser and your always-on Hermes agent can act on Asana for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Asana.
- 1
Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable - 2
Connect Asana
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Asana?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Asana in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
List my tasks in the <workspace> workspace with asana_get_multiple_tasks, pick the one titled '<task title>', then update it with asana_update_a_task using the real gid from the list. Quote the updated fields.
Using a different agent?
The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Asana is connected in the dashboard, that agent calls the same 247 Asana tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Asana MCP for Hermes
Looking for a Asana MCP server for Hermes Agent? ClawLink connects Asana to Hermes Agent and exposes 247 Asana tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Asana integration works the same way.
Hermes Agent is the MCP-native agent runtime from Nous Research, and this page is about giving that runtime Asana tools it can call from chat. You connect Asana once in the browser and ClawLink hosts the OAuth flow, so there is no personal access token to generate in Asana's developer console and no environment file to edit. The plugin installs from the ClawLink-HQ/hermes-plugin repository with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pairing is hermes clawlink begin, approve in the browser, hermes clawlink finish. Those are the exact commands, because search engines currently teach a variant that does not exist.
What the Hermes Agent Asana integration can do
247 Asana tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 247.
30 of 247 Asana tools for Hermes
| Tool | What it does |
|---|---|
Add followers to project asana_add_followers_to_project | Add followers to an Asana project |
Add followers to task asana_add_followers_to_task | Add followers to an Asana task |
Add members to project asana_add_members_to_project | Add users to an Asana project |
Add tag to task asana_add_tag_to_task | Add an existing tag to an Asana task |
Add task dependencies asana_add_task_dependencies | Add dependency relationships to an Asana task |
Add user to team asana_add_user_to_team | Add a user to a team in Asana |
Add user to workspace asana_add_user_to_workspace | Add a user to an Asana workspace |
Approve access request asana_approve_access_request | Approve an access request in Asana |
Get a project asana_get_a_project | Retrieves a specific Asana project by its project_gid, with an option to include additional |
Get a task asana_get_a_task | Retrieves full details for a specified task GID accessible by the user; use opt_fields to |
Get a user task list asana_get_a_user_task_list | Retrieves a user's Asana task list for a specified workspace, using the user GID or me in |
Get access requests asana_get_access_requests | Retrieve access requests for a target object |
Get AI studio runs asana_get_ai_studio_runs | Get AI Studio credit utilization |
Get AI studio seats asana_get_ai_studio_seats | Get AI Studio seats |
Get allocation asana_get_allocation | Get an allocation by ID |
Get allocations asana_get_allocations | Get multiple allocations |
Get attachment asana_get_attachment | Get a single attachment by its globally unique identifier |
Get audit log events asana_get_audit_log_events | Retrieve audit log events for a workspace or organization, with optional filters |
Get budget asana_get_budget | Get a budget |
Get budgets asana_get_budgets | Get all budgets |
Get current user asana_get_current_user | Retrieve the authenticated user, including accessible workspaces, for establishing user context |
Get custom field asana_get_custom_field | Retrieve a custom field by its globally unique identifier, with optional selection of returned |
Get custom field settings for goal asana_get_custom_field_settings_for_goal | Get a goal's custom fields |
Get custom field settings for portfolio asana_get_custom_field_settings_for_portfolio | Get a portfolio's custom fields |
Get custom field settings for team asana_get_custom_field_settings_for_team | Get a team's custom fields |
Get custom fields for workspace asana_get_custom_fields_for_workspace | List custom fields in a workspace, returning a page of results and pagination information when |
Get custom type asana_get_custom_type | Get a custom type |
Get custom types asana_get_custom_types | List custom types associated with a project, returning a page of results and pagination |
Get events asana_get_events | Retrieve events on an Asana resource to monitor changes using a sync token |
Get favorites for user asana_get_favorites_for_user | Get a user's favorites of a selected resource type within a workspace, ordered as they appear |
Try it: find the Asana tool you need
Browse the 30 Asana tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
List my tasks in the <workspace> workspace with asana_get_multiple_tasks, pick the one titled '<task title>', then update it with asana_update_a_task using the real gid from the list. Quote the updated fields.
How the Asana tools take their arguments
These four details, verified against the live tool schemas, are the difference between a tool that works and a 403 or 404.
- Asana ids are global unique ids (gids), not numeric ids. Every tool that addresses a task, project, workspace, or user takes a
gid. Example ids from documentation fail exactly like real typos do. opt_fieldsis how you ask for more.asana_get_a_taskreturns the task's core fields; the schema says to useopt fieldsto customize returned data. If a field is missing from a result, the tool call needs the opt_fields argument, not a different tool.- The task list filters are coupled.
asana_get_multiple_tasksaccepts anassigneefilter only together with aworkspace, and aworkspacefilter together with anassignee. Passing one without the other is a documented requirement in the schema. - Task creation needs an anchor.
asana_create_a_taskrequires aworkspace, aparent, orprojectsto associate the task, andfollowers,projects, andtagsare set only at creation, not later.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Asana working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Asana app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Asana through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Asana. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Asana actions to the runtime in a format your agent can reliably use. | 247 tools for Asana are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Asana to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Asana in the browser, and the 247 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Asana
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Connection succeeds but no tools appear
Reconnect Asana from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Asana tools
Asana tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Asana call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Asana returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
Asana API 403 insufficient permissions
Search engines answer this shape with Asana's own vocabulary, and the two causes they teach map onto this integration. First: the connected account is not a member of the project or does not hold the granular role the action needs. Asana's roles are Admin, Editor, and Commenter, and several tools (adding members, changing project fields) need at least Editor on that project. Second, and this is the cause the engines never teach: the agent passed a placeholder id from documentation, like an example gid, instead of a real one. Asana ids are global unique ids, not numbers you can guess. Ask the agent to run a list tool like asana_get_multiple_tasks or asana_get_multiple_projects first and retry with the real gid from the result.
Ask the agent to diagnose it:
Call asana_get_current_user and then asana_get_multiple_projects, tell me which workspaces and projects the account can see, then run the failing tool once more and quote the exact error.Asana MCP tool not found
On this SERP the error usually belongs to Asana's own MCP server, not to a hosted plugin: Asana shut down its V1 MCP endpoint and clients must point at https://mcp.asana.com/v2/mcp, clear the local mcp-remote cache, and re-authenticate. If you are running Asana's official server, that is the fix. On the ClawLink hosted flow the equivalent error is 'Tool schema not loaded yet': schemas load on demand the first time a tool runs, so wait a few seconds and retry, and reconnect from the dashboard only if every call fails in a fresh chat.
OAuth finished in the browser but the account is still missing
Try reconnecting Asana and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a Hermes Agent Asana integration?
Yes. ClawLink is the fastest way to connect Hermes to Asana: link your Asana account once in the browser and Hermes Agent can call the Asana API through 247 ready-made tools — no custom code or token handling.
How do I connect Asana to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Asana in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.
How long does it take to connect Asana to Hermes Agent?
About two minutes. Sign in, click Connect next to Asana in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Asana up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Asana working from chat.
Which Hermes is this?
Hermes Agent, the Nous Research agent runtime. ChatGPT asked 'which Hermes' on 2 of 3 runs of the head query, so the disambiguation is worth one sentence: this page is about the Hermes Agent runtime, not the Hermes ecosystem's other tools or any product named after the Greek god. If you run Hermes Agent and want Asana from chat, this is the integration you would connect.
Do I still need an Asana personal access token?
No. The connection is hosted OAuth: you sign in to Asana in the browser once, and the token lives on the ClawLink server, not in a config file on your machine. You never open Asana's developer console. What you do keep is your Asana account's permissions, which is the point: the agent acts with the same access your account has, and Asana's own per-account rules still apply to every call.
Is it safe to connect Asana to an AI agent?
The connection uses Asana's OAuth consent flow, the same mechanism Asana uses for any third-party app: you approve the scopes on Asana's own screen, the agent never sees your password, and the connection can be removed from the ClawLink dashboard at any time, after which Asana rejects further calls. The practical boundary to know is that your agent can do whatever your Asana account can do, so connect with the account whose permissions you intend it to have.
Hermes paired but still can't use Asana
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Related
Ambiguous
Operate an Ambiguous workspace through its provider-hosted MCP server, including documents, spreadsheets, tasks, CRM, calendar, mail, chat, and administration.
Basecamp tools
Manage projects, to-do lists, messages, and team collaboration
Moco tools
MOCO is a business management software offering project management, time tracking, and invoicing solutions.