> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/getting-started/task-management-systems/all-supported-task-trackers/clickup.md).
# ClickUp
This one-time setup *per workspace* allows everyone in your Aikido organization to create issues directly in ClickUp.
Following use cases are supported :
* **Automated Ticket Creation**: Automatically create and push tickets to specified ClickUp projects for seamless tracking of security issues.
* **Manual Ticket Addition**: Manually add security issue tickets to ClickUp, ensuring targeted attention for critical vulnerabilities.
## Connecting the Aikido App to ClickUp
1. Navigate to [Integration Settings](https://app.aikido.dev/settings/integrations) within the Aikido app.
2. In the 'Task Trackers' section, select 'ClickUp'
3. A prompt will request authorization for ClickUp.\
β
4. Login into your ClickUp account
5. Grant Aikido permission to access your ClickUp workspace
6. Once authorized, Aikido is successfully connected to ClickUp, enhancing your task management capabilities π
## βOptions for Task Creation in ClickUp via Aikido
There are two different options to create new tasks from Aikido into ClickUp.
1. Manually create tasks from the Aikido interface
2. Automatically create new tasks via Aikido's auto creation functionality.
## 1. Manual Task Creation
1. Hover over any issue in your feed and click the ***+*** in the **assignee column.**\
β
Alternatively, you can click the triple dots in the last columns to open up the action menu. If you have grouped issues, the triple dot action menu is available on every subissue.\
β
2. Fill in the required details in the popup modal.\
β
3. The newly created task in ClickUp will be linked in the Aikido Issue Detail under the 'Tasks' tab (sidepanel).
## 2. Automated Task Creation
{% hint style="info" %}
Aikido will automatically create tasks **every hour in bulk.** There is at the moment no option to trigger this manually.
{% endhint %}
1. Go to the [ClickUp Integration](https://app.aikido.dev/settings/integrations/tasktracker) settings
2. Make sure to enable '**Autocreation**' by clicking the toggle to **On.**
3. Define the criteria for automatic task creation.
You can configure all of these settings in the autocreation modal:
* **On/Off:** Enable or disable autocreation. When off, the threshold is effectively set to `None`.
* **Severity threshold:** Create tickets for issues at `Critical`, `High`, `Medium`, or `Low` and above. For example, `High` creates tickets for `High` and `Critical`.
* **Issue types:** Create tickets for all issue types, or limit them to specific types like `SCA`, `SAST`, `Secrets`, `Cloud`, `IaC`, `Malware`, or `License`.
* **Daily limit:** Set the maximum number of tickets created per day. The default is `25`. Some plans support higher limits.
* **Ticket creation mode:** Create one ticket per issue group, or create separate tickets per location or scope. Per-location mode can create more tickets.
* **Scope:** Available only in per-location mode. Target all repos or clouds, only mapped repos or teams, or specific repos or clouds with include and exclude lists.
4. Aikido will then autonomously generate ClickUp tickets based on these settings π
## Map Aikido data to custom fields
Aikido can fill ClickUp custom fields on every task it creates. Use it to send severity, SLA dates, links, and other Aikido data straight into your ClickUp fields.
### Supported field types
| ClickUp field type | Example value |
| --------------------- | --------------------- |
| Text | `Severity: $SEVERITY` |
| Text area (long text) | `$TLDR` |
| Website | `$AIKIDO_LINK` |
| Number | `$SEVERITY_SCORE` |
| Dropdown | `$SEVERITY` |
| Labels | `label 2, label 3` |
| Date | `$SLA_DATE` |
| Checkbox | `true` |
For **Dropdown** and **Labels** fields, enter the option names exactly as they appear in ClickUp. You don't need option IDs.
### Configure field mappings
1. Go to [**Integrations** β **ClickUp** β **Field Mapping**](https://app.aikido.dev/settings/integrations/tasktracker/fields/custom) and click **Add Field**.
2. Enter the ClickUp custom field name in **Custom Field**, exactly as it appears in ClickUp.
3. Enter an Aikido shortcode (e.g. `$SEVERITY`) or a fixed text value in **Aikido Value**.
4. Click **Save Changes**.
The **Preview** column shows the value Aikido will send to ClickUp.
### Fixed values and shortcodes
**Fixed values:** Enter plain text to set the same value on every task. For example, `Security` fills that field with "Security" on every task Aikido creates.
**Shortcodes:** Aikido replaces shortcodes with data from the issue when it creates the task. You can combine them with fixed text, such as `Issue: $TLDR` or `Detected on $FIRST_DETECTED_DATE`. For the full list of shortcodes, see [Map Aikido Data to Jira Custom Fields](/getting-started/task-management-systems/map-aikido-data-to-jira-custom-fields.md). The same shortcodes work for ClickUp.
For ClickUp **Date** fields, use the `YYYY-MM-DD` format (e.g. `2024-10-23`) or the `_DATE` shortcodes, such as `$SLA_DATE`.
***
---
# 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://help.aikido.dev/getting-started/task-management-systems/all-supported-task-trackers/clickup.md?ask=&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.
