Asana + LangGraph

How to connect Asana to LangGraph

Use LangGraph with Agent200 for read-only Asana task briefings. Check owners, deadlines and completion states with the user's own connection.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Asana tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Build a LangGraph flow that separates task resolution, tool execution and summarization. Keep the authenticated application user attached to the run. Use an explicit clarification path for missing or ambiguous identifiers and an error path for refused calls, so a failed read cannot become a plausible-looking handoff.

The Agent200 SDK examples on this page are conceptual. Use the actual runtime tool definitions and supported client interfaces supplied to your application. No package installation command, parameter mapping or end-to-end runtime test is implied.

Product reference: LangGraph documentation. For Asana task fields and optional field selection, see Asana’s task-read reference.

Connector
Asana
Works with
LangGraph ยท Agent framework
Authentication
Managed OAuth, per end user
Tools
6 tools

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Asana enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a Asana account. They approve access once, on Asana's own page.
  • A LangGraph agent in your project. Agent200 gives it the tools; your code keeps the orchestration.

Connect Asana to LangGraph

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page. Enable Asana and the read operations needed for this task in your project. Keep credentials out of chats and source control.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Define the task-reading contract

    Select the existing Asana task-read operation from the tool definitions supplied by your runtime. Validate the selected task ID and map only documented inputs and outputs. Keep credentials on the server.

  3. 3

    Step 3: Connect the end user's Asana account

    Have the end user complete the Asana authorization flow. Use the same authenticated application user for connection and later requests. Confirm that the user can open the task selected for the first read.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Asana account, once.
    const connection = await agent200
      .user("user_123")
      .connect("asana");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  4. 4

    Step 4: Build the read-only briefing flow

    Use the selected task’s returned details to produce the briefing. Handle missing fields and refused calls explicitly. The following snippet is a conceptual illustration of the site’s Agent200 flow; adapt the implementation to your real runtime contract.

    langgraph-asana.js
    Conceptual example
    Guide: hand the connector's tools to an agent framework
    // The Asana tools for this user, ready for a LangGraph agent.
    const tools = await agent200
      .user("user_123")
      .tools(["asana"]);
    
    // Give `tools` to your LangGraph agent.
    // Every call it makes runs through Agent200 with the user's own connection.

Test your connection

Run one request to check everything is wired up.

Ask

For the user-selected Asana task, read its details and produce a handoff. If the identifier is missing or ambiguous, ask for clarification before the read. If access fails, return the failure instead of a fabricated handoff.

What should come back

  • The selected task is identified clearly.
  • The answer uses only the task information returned, including owner, due date and completion state when available.
  • Missing fields and access failures are reported without guessing; no Asana records are changed.

If authorization is requested, complete it with the intended Asana account. If a tool or field is unavailable, report it and check the actual tool definition. Workspace task search has separate premium access requirements.

Get your API key

Create a key in the Agent200 dashboard. It reaches Asana and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Asana to LangGraph.

Agent brief
Goal: connect Asana to LangGraph with Agent200.
Guide: https://www.agent200.com/connectors/asana/framework/langgraph/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Make sure Asana is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Give every request a stable id for the end user. Agent200 uses only that user's own connections.
5. Connect the user's Asana account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Asana.
6. Load the user's Asana tools ("asana") from Agent200 and give them to the LangGraph agent. Every call it makes runs through Agent200.
7. Check it works with this request: "For the user-selected Asana task, read its details and produce a handoff. If the identifier is missing or ambiguous, ask for clarification before the read. If access fails, return the failure instead of a fabricated handoff."
   What should come back:
   - The selected task is identified clearly.
   - The answer uses only the task information returned, including owner, due date and completion state when available.
   - Missing fields and access failures are reported without guessing; no Asana records are changed.
8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Asana, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

The whole guide is also available as Markdown, for agents and LLMs: /connectors/asana/framework/langgraph.md

Asana tools LangGraph can call

  • Read a task

    Read
    asana_get_task

    Retrieve an Asana task's details, including its description, assignee, due date and completion status.

  • Search tasks

    Read
    asana_search_tasks

    Search workspace tasks by text and filters. Requires Asana premium search access.

  • List project tasks

    Read
    asana_list_project_tasks

    List the tasks in a selected project, then read individual tasks for descriptions, ownership and deadlines.

  • List subtasks

    Read
    asana_list_subtasks

    List the subtasks of a parent task so your agent can inspect the smaller work items behind it.

  • List projects

    Read
    asana_list_projects

    List projects in a workspace to find the project relevant to a request.

  • Read a project

    Read
    asana_get_project

    Read a project's name and description to understand its purpose and context.

How it works

  1. 01

    Your app sends the request

    It calls Agent200 with the model, instructions, the input, the end user's id and the Asana tools.

  2. 02

    Your LangGraph agent picks a tool

    It calls a Asana tool when its plan needs one, with the arguments it chooses.

  3. 03

    Agent200 runs the call

    It uses that user's own Asana connection, within the endpoints and scopes your project allows, and returns the result to the model.

  4. 04

    Your app gets the result

    Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Asana account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Asana enforces what its API grants.

Troubleshooting

The task is missing or cannot be read

Confirm the task ID and that the connected Asana user can open it. An access error is not an empty task. Ask for the right task rather than guessing an ID or claiming a result.

The answer omits the owner or deadline

Check the fields actually returned by the tool. An omitted field does not prove a task is unassigned or has no due date. Report unavailable information explicitly.

Task search fails even though a task read works

Asana workspace task search requires premium eligibility and may lag recent changes. Use an identified accessible task for the first test. See Asana’s search requirements.

FAQ

What belongs in graph state?

Keep the selected task identifier, the request's user context, returned task information and any error or clarification state. Keep credentials out of graph messages and persisted checkpoints. Use actual tool schemas supplied by your runtime instead of inferring an Agent200 adapter API.

Use Asana with another framework

200 OK

Asana, connected to LangGraph.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)