> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/connect/clickup.md). # ClickUp ## Connection When you're setting up your first workflow with ClickUp, you will need to create a [connection](https://docs.getmesa.com/going-further/credential) in order to connect MESA with ClickUp.
Screenshot of the ClickUp step in the MESA workflow builder. Spotlight the Sign in with ClickUp button.
Click Sign in with ClickUp to login to your account and connect your Workspace with MESA. Once that's done, your connection is complete. ## Technical Notes ### ClickUp Free Plan: Custom Field Limits #### What's the limitation? ClickUp's Free Forever plan limits how many times custom fields can be set across tasks in a space. #### Why does this affect workflows? Automated workflows can hit this limit faster than manual use. #### Common problems * Workflow fails * Error mentions "Custom field usages exceeded" #### How to fix it * Remove unused custom fields in ClickUp * Reduce how often workflows set custom fields * Upgrade your ClickUp plan #### Example A workflow that updates 3 custom fields on every new task will hit the limit faster than expected. ### Task Update Trigger Adding an attachment to a task won't run the Task Update trigger, but uploading an attachment to a task comment will. --- # 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.getmesa.com/connect/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.