# Clickup

### Prequisites

* A Clickup account with sufficient permissions

Important note: the scope of the data which will be synchronized to Coworker is defined by the user behind the API key.\
We recommend that you create a service account which will have the right permissions, ie. no access to sensitive tasks/data.

### Generating the credentials

Log in as the service account which will make the API key, and go to your [settings page](https://app.clickup.com/settings/apps)

<figure><img src="https://3561055466-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fcl1KIMhPQkmG41x5eGvL%2Fuploads%2FvuMFIbkwwGpAUQ4U46HI%2FScreenshot%202024-07-26%20at%2014.45.40.png?alt=media&#x26;token=00a16896-3d05-471a-b8e6-da08ae2a7823" alt="" width="563"><figcaption></figcaption></figure>

Click on "Generate" to generate the access token

### Information required for the Coworker connection:

* `api_token`: the API token generated above
* `team_id`: the unique ID referencing your team. This can be found in your Clickup URL, ie. <https://app.clickup.com/20596928/home> -> 20596928


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://village-labs.gitbook.io/coworker-product-and-developer-docs/data-connections/clickup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.