Skip to main content
Book a demo

Connect Asana to Claude

Give Claude governed access to Asana’s 39 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add Asana to Claude in four steps

Admins approve the server once. Everyone in Claude then gets it through the same governed connection.

  1. 1

    Approve Asana in Runlayer

    Add Asana from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Asana’s 39 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 3

    Sign in to Asana

    Each user signs in to Asana with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Asana from Claude

    Asana’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

39 Asana tools in Claude

Runlayer policy decides which of these Claude users can call.

  • Add comment

    Add a comment to a task.

  • Create project

    Create a new project with optional sections and tasks in a single operation.

  • Create project confirm

    DEPRECATED; DO NOT USE.

  • Create project confirm populate

    DEPRECATED; DO NOT USE.

  • Create project from template

    Create a project from a project template.

  • Create project preview v3

    Show a visual preview of a project structure before the project is created in Asana.

  • Create project status update

    Post a status update to a project or portfolio.

  • Create task confirm

    DEPRECATED; DO NOT USE.

See all 39 Asana tools

Control

What Runlayer can see and stop in Claude

Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.

  • Gateway policy (available)

    Every Asana call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination