# How to connect ClickUp to LangGraph

> Give LangGraph access to ClickUp through Agent200: managed OAuth, ready-made tools and one API key.

- Page: https://www.agent200.com/connectors/clickup/framework/langgraph/
- Connector: [ClickUp](https://www.agent200.com/connectors/clickup.md)
- Framework: LangGraph
- Updated: 2026-11-18

## Instructions for AI agents

Goal: connect ClickUp to LangGraph with Agent200.
Guide: https://www.agent200.com/connectors/clickup/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 ClickUp 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 ClickUp account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on ClickUp.
6. Load the user's ClickUp tools ("clickup") 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 ClickUp 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 preserves its returned status, includes all returned assignees and reports its due date when available.
   - Missing data and access failures are stated clearly; no ClickUp records or comments 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 ClickUp, then retry.

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

## 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](https://docs.langchain.com/oss/python/langchain/mcp). For task identity and response scope, see [ClickUp’s task reference](https://developer.clickup.com/reference/gettask).

- **Connector:** [ClickUp](https://www.agent200.com/connectors/clickup/)
- **Works with:** LangGraph · Agent framework
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [8 tools](https://www.agent200.com/connectors/clickup/framework/langgraph/#tools)

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **ClickUp enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a ClickUp account.** They approve access once, on ClickUp's own page.
- **A LangGraph agent in your project.** Agent200 gives it the tools; your code keeps the orchestration.

## Connect ClickUp to LangGraph

### Step 1: Create your Agent200 API key

Create a key on the [API keys page](https://agent200.com/platform/apikeys/). Enable ClickUp and the read operations needed for this task in your project. Keep credentials out of chats and source control.

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Define the task-reading contract

Select the existing ClickUp 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.

### Step 3: Connect the end user's ClickUp account

Have the end user complete the ClickUp 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.

File `connect.js`:

```js
// Each end user authorizes their own ClickUp account, once.
const connection = await agent200
  .user("user_123")
  .connect("clickup");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

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

File `langgraph-clickup.js`:

```js
// The ClickUp tools for this user, ready for a LangGraph agent.
const tools = await agent200
  .user("user_123")
  .tools(["clickup"]);

// Give `tools` to your LangGraph agent.
// Every call it makes runs through Agent200 with the user's own connection.
```

(Conceptual example of the Agent200 SDK.)

## Test your connection

Ask: "For the user-selected ClickUp 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 preserves its returned status, includes all returned assignees and reports its due date when available.
- Missing data and access failures are stated clearly; no ClickUp records or comments are changed.

Use a task the connected user can open in the authorized Workspace. Check the runtime schema if using a custom task ID. Report missing data and preserve the task’s returned status label.

## ClickUp tools LangGraph can call

- **Read a task** (`clickup_get_task`, read): Retrieve a task’s description, status, assignees and due date when available.
- **List tasks** (`clickup_list_tasks`, read): Read tasks in a selected List, with attention to pagination and the requested task filters.
- **Read task comments** (`clickup_get_task_comments`, read): Read comments on a task to add discussion context to a handoff.
- **Read a List** (`clickup_get_list`, read): Read a List’s details to understand the container for the selected work.
- **List Lists in a Folder** (`clickup_list_lists`, read): Find the Lists inside a selected Folder.
- **List folderless Lists** (`clickup_list_folderless_lists`, read): Find Lists that sit directly in a Space rather than inside a Folder.
- **List Folders** (`clickup_list_folders`, read): Read the Folders in a selected Space to locate the work the user requested.
- **List Spaces** (`clickup_list_spaces`, read): Read the Spaces available in a selected Workspace.

## How it works

1. **Your app sends the request.** It calls Agent200 with the model, instructions, the input, the end user's id and the ClickUp tools.
2. **Your LangGraph agent picks a tool.** It calls a ClickUp tool when its plan needs one, with the arguments it chooses.
3. **Agent200 runs the call.** It uses that user's own ClickUp connection, within the endpoints and scopes your project allows, and returns the result to the model.
4. **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 ClickUp account.

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

## Troubleshooting

### The task cannot be found or read

Check the selected task and authorized ClickUp Workspace. Distinguish native task IDs from custom IDs and use the inputs your tool actually supports. Report a refused call instead of guessing a task or a successful result.

### The answer names only one person or changes the status meaning

Compare the answer with the returned record. Keep every returned assignee and the recorded status label. A missing field is not evidence that a task is unassigned or complete.

### The List summary seems incomplete

Check pagination and the task filters available in the runtime. State the result scope and avoid treating one page as the full List. See [ClickUp’s List task reference](https://developer.clickup.com/reference/gettasks).

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

### How should the graph handle a partial List result?

Keep pagination and the requested scope in graph state. Separate a successful page read from a completed List traversal, and summarize only the records actually collected. Stop with a clear error or partial-result label if the traversal fails.

## Use ClickUp with another framework

- [ClickUp + Claude](https://www.agent200.com/connectors/clickup/framework/claude.md)
- [ClickUp + ChatGPT](https://www.agent200.com/connectors/clickup/framework/chatgpt.md)
- [ClickUp + Claude Code](https://www.agent200.com/connectors/clickup/framework/claude-code.md)
- [ClickUp + Muse](https://www.agent200.com/connectors/clickup/framework/muse.md)
- [ClickUp + Grok Bot](https://www.agent200.com/connectors/clickup/framework/grok-bot.md)
- [ClickUp + OpenAI Dots](https://www.agent200.com/connectors/clickup/framework/openai-dots.md)
- [ClickUp + Claude Duet](https://www.agent200.com/connectors/clickup/framework/claude-duet.md)
- [ClickUp + Hermes Agent](https://www.agent200.com/connectors/clickup/framework/hermes-agent.md)
- [ClickUp + OpenClaw](https://www.agent200.com/connectors/clickup/framework/openclaw.md)
- [ClickUp + OpenAI Agents SDK](https://www.agent200.com/connectors/clickup/framework/openai-agents-sdk.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
