> ## Documentation Index
> Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt
> Use this file to discover all available pages before exploring further.

# ClickUp Connector

<Badge icon="arrow-left" color="gray">[Back to Search AI connectors list](/ai-for-service/searchai/content-sources#supported-connectors)</Badge>

ClickUp is a work management application for organizing tasks, setting priorities, assigning deadlines, and tracking progress. The ClickUp connector enables Search AI to ingest tasks and sub-tasks, letting users quickly search task updates, assignments, and project details.

## Specifications

| Specification     | Details             |
| ----------------- | ------------------- |
| Repository type   | Cloud               |
| Supported content | Tasks and Sub-Tasks |
| RACL support      | Yes                 |
| Content filtering | No                  |

## Prerequisites

Search AI uses the ClickUp API with a personal API token for authentication. To generate one:

1. Go to **Workspace Settings**.
2. Under **Settings**, open the **Apps** page.
3. Copy your API token. If none exists, click **Generate** to create one.

The personal API token provides access to all workspaces the user has permission to access.

## Configure the ClickUp Connector in Search AI

On the **Auth** page of the connector, provide the following details and click **Connect**.

| Field                  | Value                                   |
| ---------------------- | --------------------------------------- |
| **Name**               | Unique name for the connector           |
| **Authorization Type** | APIKey                                  |
| **API Key**            | Personal API token generated in ClickUp |

## Content Ingestion

After a successful sync, the connector ingests tasks and sub-tasks from ClickUp including:

* Task description and metadata: status, priority, start date, due date, project name, folder
* Checklists and sub-tasks associated with each task
* Attachment names and URLs (attachment content is not ingested)

## RACL Support

The `sys_racl` field for each task is populated with the **folder ID** of the folder containing the task. Tasks directly under a space have `sys_racl` set to `*`.

The folder ID is used as a permission entity. Use the Permission Entity APIs to associate users with the folder ID entity to enforce access control.