> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/ticketing/clickup.md).

# ClickUp

Connect ClickUp to Siit to escalate requests into ClickUp tasks with one click. ClickUp is the right choice when ops, project, or product teams already manage their work in ClickUp.

### What you get

* **One-click escalation from any request.** Click **Escalate ticket** in the request side panel, pick a ClickUp space, list, and assignee, and a linked task is created with the Siit context pre-filled.
* **Workflow-driven task creation.** Use **Create ClickUp task** as a workflow step, with approval gating where needed.
* **Audit trail.** Every ClickUp action triggered from Siit is recorded on the request timeline.

### How it works

1. From the request side panel, click **Escalate ticket** and pick **ClickUp**.
2. Choose the space, list, assignee, priority, and due date. Fill in the task name and description.
3. Submit. Siit creates the ClickUp task, links it back to the Siit request, and posts the link on both sides.

The same flow is available in workflows (as a **Create ClickUp task** action).

### What syncs from ClickUp

* **Tasks created from Siit** — every escalated ticket is tracked with its ClickUp task ID and link.
* **Links** — preserved between the Siit request and the ClickUp task, visible on both sides.

> **Note** — bi-directional status sync is not currently available for ClickUp. Track completion either through the ClickUp link on the request or by manually closing the Siit request when work is done.

### Custom field mapping

> **Coming soon.** Custom field mapping for ClickUp is on our roadmap. For now, you can set the standard task fields when escalating. To track which fields are exposed, reach out via the in-app chat.

### Connect ClickUp

1. In Siit, go to **Settings → Workspace → Integration library**, find **ClickUp** in the Ticketing section, and click **Connect**.
2. Sign in to ClickUp as an admin and approve the requested scopes.
3. Pick the workspace, space(s), and list(s) available for escalation.
4. Test by escalating a sample request from Siit to ClickUp.

Need a more detailed walkthrough? Reach out to support via the in-app chat.

### Common workflows

**Project request handoff.** *Trigger: Service = "Project request". Actions: Create ClickUp task in the project list → Assign to the project lead → Notify requester.*

**Tag-based routing.** *Trigger: Tag "ops-task" added. Actions: Manager approval → Create ClickUp task in the ops list → Notify requester.*

### Troubleshooting

**"Authorization failed" on connect.** The admin signing in lacks ClickUp workspace admin rights. Try with a workspace owner.

**List missing from the destination picker.** The Siit ClickUp user lacks access to that list. Update list permissions in ClickUp and re-sync.

**"Task created" but no link in Siit.** The ClickUp task was created but the back-link save failed. Open the request timeline — the ClickUp task ID is logged. Manually re-link if needed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/integrations/ticketing/clickup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.