# How to connect Asana to Hermes Agent (no API keys)

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

Web version: https://claw-link.dev/hermes/asana

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.

**Start here — paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

## Setup

It takes three steps to connect Hermes to Asana.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Asana** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect asana  # connect Asana (browser OAuth)
npx -y @useclawlink/cli actions asana  # list available actions
npx -y @useclawlink/cli run asana <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
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 test
```

Then connect Asana in the [ClawLink dashboard](https://claw-link.dev/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:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Asana is connected in the dashboard, that agent calls the same 153 Asana tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/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 153 Asana tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Asana integration](https://claw-link.dev/openclaw/asana) 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

153 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 153.

### 30 of 153 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 specific user's task list from Asana by its `user_task_list_gid`, optionally |
| **Get access requests** `asana_get_access_requests` | Retrieve access requests for a target object |
| **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` | Get audit log events for a workspace |
| **Get current user** `asana_get_current_user` | Retrieves the authenticated user's full record, including accessible workspaces, often used as |
| **Get custom field** `asana_get_custom_field` | Get a single custom field by its globally unique identifier |
| **Get custom fields for workspace** `asana_get_custom_fields_for_workspace` | Get all custom fields in a workspace |
| **Get custom types** `asana_get_custom_types` | Get all custom types associated with a project |
| **Get events** `asana_get_events` | Retrieve events on a resource to monitor changes |
| **Get favorites for user** `asana_get_favorites_for_user` | Get a user's favorites within a specified workspace |
| **Get goal** `asana_get_goal` | Retrieve the full record for a single goal by its GID |
| **Get goal relationships** `asana_get_goal_relationships` | Retrieve goal relationships |
| **Get goals** `asana_get_goals` | Retrieve multiple goals |
| **Get job** `asana_get_job` | Retrieve a job by its globally unique identifier |
| **Get membership** `asana_get_membership` | Retrieve a single membership by its ID |
| **Get memberships** `asana_get_memberships` | Retrieve memberships for goals, projects, portfolios, or custom fields |
| **Get multiple projects** `asana_get_multiple_projects` | Returns a list of projects filtered by workspace or team (one required), with optional archived |
| **Get multiple tasks** `asana_get_multiple_tasks` | Retrieves a list of tasks, allowing filtering by assignee (requires `workspace`), project |

## Example prompts

**Find and update a task**

> 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.

**Create a task and attach a project**

> Call asana_get_multiple_projects to get a real project gid, then asana_create_a_task with that project in the projects field, title '\<title>', and notes '\<notes>'. Confirm the new task gid.

**Add followers to a task**

> Find the task '\<title>' with asana_get_multiple_tasks, then add the user \<user email> as a follower with asana_add_followers_to_task using the task gid you just looked up. Confirm the follower list.

## 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_fields` is how you ask for more.** `asana_get_a_task` returns the task's core fields; the schema says to use `opt fields` to 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_tasks` accepts an `assignee` filter only together with a `workspace`, and a `workspace` filter together with an `assignee`. Passing one without the other is a documented requirement in the schema.
- **Task creation needs an anchor.** `asana_create_a_task` requires a `workspace`, a `parent`, or `projects` to associate the task, and `followers`, `projects`, and `tags` are 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. | 153 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 153 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](https://claw-link.dev/hub/composio-alternatives) comparison.

### 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:

```text
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.

### 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 153 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

- [DocuSign](https://claw-link.dev/hermes/docusign) — Send, sign, and manage agreements and envelopes
- [Moco tools](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.
- [Connect Wrike](https://claw-link.dev/hermes/wrike) — Manage projects, tasks, and team workflows at scale