Skip to main content
Integrations · Asana
Guild agents create, update, and search Asana tasks, and read projects, sections, portfolios, goals, and teams through the Asana REST API. Guild stores your Asana token and injects it server-side, so agent code never sees it. Credential policies decide which Asana operations each agent may call.

Book a demo

See how teams govern agents that use Asana.

Talk to sales

Get access to Guild, then connect Asana to your first agent.

What the Asana integration exposes

The integration is guildai~asana-openapi. It is generated from Asana’s OpenAPI description, which is what the -openapi suffix means: agents call the Asana REST API at https://app.asana.com/api/1.0, not Asana’s MCP server. Tools cover tasks, subtasks, dependencies, stories and comments, projects, sections, tags, custom fields, portfolios, goals, status updates, teams, users, and workspaces.

How it works

1

Create an Asana token

In Asana, open the developer console, click Create new token, and copy it. The token acts as you, so the agent sees what you can see.
2

Connect the token in Guild

Go to Access & setup > Credentials, click Connect, select asana-openapi, and paste the token into API Key.
3

Import the tools you need

Import AsanaOpenapiTools from @guildai-services/guildai~asana-openapi and use pick() to give the agent only the tools its job needs.

Why Asana access needs governing

A personal access token carries your full Asana permissions, including deleting tasks, projects, and sections. Guild keeps the token server-side and checks every request against your credential policies before it reaches Asana. A policy can allow an agent to read and comment on tasks while denying deletes, and you can scope a credential to one workspace or one agent.

Authentication

  • Type: API key
  • Header: Guild sends the token as Authorization: Bearer <token>
  • Token: an Asana personal access token. It doesn’t expire, but you can revoke it in the developer console.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Tools are named with the asana_openapi_ prefix. The integration has more than 160 tools, so pick the ones the agent needs rather than spreading the whole set.

Tools

Tools in the latest published version of guildai~asana-openapi:

Frequently asked questions

No. It authenticates with a personal access token and calls the Asana REST API directly. The token acts as the person who created it.
Not yet. The integration includes Asana’s webhook management tools, but Guild doesn’t receive Asana events, so you can’t create an event trigger for Asana. Run the agent on a schedule instead.
Yes. Write a credential policy that denies the delete operations, such as asana_openapi_delete_task. A DENY rule always overrides an ALLOW rule. See Credential policies.
Also runs on Guild: Jira · Linear · Google Calendar Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 4, 2026