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

# ClickUp Webhook Setup Guide

> Configure ClickUp to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/clickup#getting-started) on the ClickUp connector page.

<section data-guide-section data-guide-scopes="">
  <h2>How webhooks are set up</h2>

  <p>ClickUp delivers events through a webhook subscription, and StackOne provisions it for you on connection. When you connect your account, StackOne creates one ClickUp webhook subscription (`POST /team/{workspaceId}/webhook`) pointing at a StackOne callback URL, covering every supported event type for your configured Workspace ID. When you disconnect, StackOne deletes that subscription (`DELETE /webhook/{id}`). There is nothing to set up in ClickUp and no URL to paste.</p>

  <Steps>
    <Step title="Connect with a Personal API Token or OAuth 2.0">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Authorize the connection with either auth type — both work the same way for webhooks — so StackOne can create and delete the subscription on your behalf. No further setup is needed in ClickUp.</p>
      </div>
    </Step>

    <Step title="Enable the events you need">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Enable the ClickUp events you want in StackOne. StackOne registers one consolidated subscription that already covers every event type; only the events you enable in StackOne are dispatched onward.</p>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>How events are delivered</h2>

  <p>ClickUp signs each delivery with a single `X-Signature` header (an HMAC-SHA256 hex digest of the raw request body). Because the signing secret is generated by ClickUp itself and is only handed back once — at the moment the subscription is created — StackOne cannot store it for later use, so it does not recompute the full signature on incoming requests. The per-account callback URL is the security boundary for these deliveries.</p>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available webhook events</h2>

  <p>The events below can be enabled for this connection, grouped by the entity they apply to.</p>

  <Steps>
    <Step title="Task events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Fired for tasks.</p>

        <ul>
          <li><strong>Task Created</strong> (`taskCreated`) — Fired when a task is created.</li>
          <li><strong>Task Updated</strong> (`taskUpdated`) — Fired when a task's properties are modified generically.</li>
          <li><strong>Task Deleted</strong> (`taskDeleted`) — Fired when a task is deleted.</li>
          <li><strong>Task Priority Updated</strong> (`taskPriorityUpdated`) — Fired when a task's priority changes.</li>
          <li><strong>Task Status Updated</strong> (`taskStatusUpdated`) — Fired when a task's status changes.</li>
          <li><strong>Task Assignee Updated</strong> (`taskAssigneeUpdated`) — Fired when assignees are added to or removed from a task.</li>
          <li><strong>Task Due Date Updated</strong> (`taskDueDateUpdated`) — Fired when a task's due date changes.</li>
          <li><strong>Task Tag Updated</strong> (`taskTagUpdated`) — Fired when tags are added to or removed from a task.</li>
          <li><strong>Task Moved</strong> (`taskMoved`) — Fired when a task is moved between lists.</li>
          <li><strong>Task Comment Posted</strong> (`taskCommentPosted`) — Fired when a new comment is added to a task.</li>
          <li><strong>Task Comment Updated</strong> (`taskCommentUpdated`) — Fired when a comment on a task is edited.</li>
          <li><strong>Task Time Estimate Updated</strong> (`taskTimeEstimateUpdated`) — Fired when a task's time estimate changes.</li>
          <li><strong>Task Time Tracked Updated</strong> (`taskTimeTrackedUpdated`) — Fired when tracked time on a task changes.</li>
        </ul>
      </div>
    </Step>

    <Step title="List events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Fired for lists.</p>

        <ul>
          <li><strong>List Created</strong> (`listCreated`) — Fired when a list is created.</li>
          <li><strong>List Updated</strong> (`listUpdated`) — Fired when a list's properties change.</li>
          <li><strong>List Deleted</strong> (`listDeleted`) — Fired when a list is deleted.</li>
        </ul>
      </div>
    </Step>

    <Step title="Folder events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Fired for folders.</p>

        <ul>
          <li><strong>Folder Created</strong> (`folderCreated`) — Fired when a folder is created.</li>
          <li><strong>Folder Updated</strong> (`folderUpdated`) — Fired when a folder's properties change.</li>
          <li><strong>Folder Deleted</strong> (`folderDeleted`) — Fired when a folder is deleted.</li>
        </ul>
      </div>
    </Step>

    <Step title="Space events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Fired for spaces.</p>

        <ul>
          <li><strong>Space Created</strong> (`spaceCreated`) — Fired when a space is created.</li>
          <li><strong>Space Updated</strong> (`spaceUpdated`) — Fired when a space's properties change.</li>
          <li><strong>Space Deleted</strong> (`spaceDeleted`) — Fired when a space is deleted.</li>
        </ul>
      </div>
    </Step>

    <Step title="Goal events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Fired for goals.</p>

        <ul>
          <li><strong>Goal Created</strong> (`goalCreated`) — Fired when a goal is created.</li>
          <li><strong>Goal Updated</strong> (`goalUpdated`) — Fired when a goal's properties change.</li>
          <li><strong>Goal Deleted</strong> (`goalDeleted`) — Fired when a goal is deleted.</li>
        </ul>
      </div>
    </Step>

    <Step title="Key result events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Fired for key results (measurable targets within a goal).</p>

        <ul>
          <li><strong>Key Result Created</strong> (`keyResultCreated`) — Fired when a key result is created.</li>
          <li><strong>Key Result Updated</strong> (`keyResultUpdated`) — Fired when a key result's progress or properties change.</li>
          <li><strong>Key Result Deleted</strong> (`keyResultDeleted`) — Fired when a key result is deleted.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.