<!-- BusyBot node reference — https://busybot.net/tools/clickup-trigger/ -->

> Node: ClickUp Trigger (`clickup_trigger`) · Webhook trigger · v1
> Category: Productivity · Credentials: ClickUp API (`clickupApi`)
> Updated: 2026-08-16

# ClickUp Trigger

> Trigger workflows from ClickUp events

## Overview

The ClickUp Trigger node listens for webhook events from a ClickUp workspace. It can be configured to trigger on specific events such as task creation, task updates, task deletion, comments, folder changes, goal changes, and more. The incoming webhook payload contains full event details including the affected resource ID, event type, and history entries describing what changed. Supports filtering by space, folder, list, or task ID. Verifies webhook authenticity via HMAC SHA-256 signature.

**Category:** Productivity  
**Tool Name:** `clickup_trigger`  
**Version:** 1

**Appearance:** Icon: `si-clickup` | Color: `#7b68ee`

## Node Type

**Trigger** — webhook (receives incoming HTTP callbacks)

## Input / Output

| Direction | Port(s) |
|-----------|--------|
| Input | None (trigger node) |
| Output | `Output` |

## Credentials

This tool requires **ClickUp API** credentials.
See the [Credentials Guide](https://busybot.net/credentials/clickup-api/) for setup instructions.

### Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| Team ID | `string` | Yes | — | The ClickUp team (workspace) ID. Find this in your ClickUp workspace settings or via the ClickUp API. |
| Events | `multiOptions` | Yes | `[]` | Which ClickUp events to listen for. Select * to receive all events. |
| | | | | Options: `*` (All Events), `folderCreated`, `folderDeleted`, `folderUpdated`, `goalCreated`, `goalDeleted`, `goalUpdated`, `keyResultCreated`, `keyResultDeleted`, `keyResultUpdated`, `listCreated`, `listDeleted`, `listUpdated`, `spaceCreated`, `spaceDeleted`, `spaceUpdated`, `taskAssigneeUpdated`, `taskCommentPosted`, `taskCommentUpdated`, `taskCreated`, `taskDeleted`, `taskDueDateUpdated`, `taskMoved`, `taskStatusUpdated`, `taskTagUpdated`, `taskTimeEstimateUpdated`, `taskTimeTrackedUpdated`, `taskUpdated` |
| Filters | `collection` | No | `{}` | Optionally scope the webhook to a specific space, folder, list, or task. |
| — Folder ID | `string` | No | — | Only receive events for this folder |
| — List ID | `string` | No | — | Only receive events for this list |
| — Space ID | `string` | No | — | Only receive events for this space |
| — Task ID | `string` | No | — | Only receive events for this task |

## Output Data

Each delivery from ClickUp produces one output item. The webhook payload is copied onto the item unchanged, and three fields are added:

- `_trigger` — always `clickup_webhook`
- `_timestamp` — ISO 8601 timestamp of when the request arrived
- `_webhookEvent` — the ClickUp event name, taken from the payload's `event` field

The ClickUp payload itself carries:

- `event` — the event name, e.g. `taskCreated`
- `webhook_id` — the ID of the ClickUp webhook that delivered the event
- `task_id` — the affected task, on task events
- `history_items` — an array of change entries, each with `field`, `before`, `after`, `date`, and `user`

Reference the payload downstream by expression, e.g. `{{ $json.task_id }}` or `{{ $json.history_items[0].after.status }}`.

## Usage Examples

- Start a workflow when a new task is created in ClickUp
- Trigger an automation when a ClickUp task status changes
- Run a workflow when someone comments on a ClickUp task
- Automate actions when a ClickUp folder or list is updated
- Listen for ClickUp goal progress updates

## Example Configuration

Listen for all task-related events across the entire workspace:

```json
{
  "type": "clickup_trigger",
  "typeVersion": 1,
  "position": [0, 0],
  "parameters": {
    "team": "1234567",
    "events": ["taskCreated", "taskUpdated", "taskDeleted"]
  }
}
```

Listen for all events but only within a specific space:

```json
{
  "type": "clickup_trigger",
  "typeVersion": 1,
  "position": [0, 0],
  "parameters": {
    "team": "1234567",
    "events": ["*"],
    "filters": {
      "spaceId": "space_123456"
    }
  }
}
```

Listen for comment events only within a specific list:

```json
{
  "type": "clickup_trigger",
  "typeVersion": 1,
  "position": [0, 0],
  "parameters": {
    "team": "1234567",
    "events": ["taskCommentPosted", "taskCommentUpdated"],
    "filters": {
      "listId": "list_789012"
    }
  }
}
```

Monitor all events for a specific task:

```json
{
  "type": "clickup_trigger",
  "typeVersion": 1,
  "position": [0, 0],
  "parameters": {
    "team": "1234567",
    "events": ["*"],
    "filters": {
      "taskId": "task_345678"
    }
  }
}
```

Monitor task status changes and assignments in a specific folder:

```json
{
  "type": "clickup_trigger",
  "typeVersion": 1,
  "position": [0, 0],
  "parameters": {
    "team": "1234567",
    "events": ["taskStatusUpdated", "taskAssigneeUpdated", "taskDueDateUpdated"],
    "filters": {
      "folderId": "folder_456789"
    }
  }
}
```

Monitor all goal and key result events:

```json
{
  "type": "clickup_trigger",
  "typeVersion": 1,
  "position": [0, 0],
  "parameters": {
    "team": "1234567",
    "events": ["goalCreated", "goalUpdated", "goalDeleted", "keyResultCreated", "keyResultUpdated", "keyResultDeleted"]
  }
}
```

Track organizational changes to spaces, folders, and lists:

```json
{
  "type": "clickup_trigger",
  "typeVersion": 1,
  "position": [0, 0],
  "parameters": {
    "team": "1234567",
    "events": ["spaceCreated", "spaceUpdated", "spaceDeleted", "folderCreated", "folderUpdated", "folderDeleted", "listCreated", "listUpdated", "listDeleted"]
  }
}
```

Monitor time-related updates in a specific space:

```json
{
  "type": "clickup_trigger",
  "typeVersion": 1,
  "position": [0, 0],
  "parameters": {
    "team": "1234567",
    "events": ["taskTimeEstimateUpdated", "taskTimeTrackedUpdated"],
    "filters": {
      "spaceId": "space_987654"
    }
  }
}
```

### Trigger Behavior

- **Activation:** When the workflow is activated, a webhook endpoint is registered with the service.
- **Deactivation:** The webhook is automatically unregistered when the workflow is deactivated.
- **Payload:** The incoming webhook payload is parsed and output as workflow items.
- **Verification:** Supports signature verification where applicable.

## Tips

Receives webhook events from ClickUp. Configure which events to listen for (task created, updated, deleted, comments, folders, goals, etc.). Optionally filter by space, folder, list, or task ID. The webhook payload includes the event type, affected resource, and change history.

### Key Notes

- The `team` parameter is always required and represents your ClickUp workspace ID
- Use `"*"` in the `events` array to listen for all available events
- Filter parameters are completely optional but help reduce noise by limiting events to specific organizational units
- The `filters` object uses a flat structure — all filter fields are direct properties of the `filters` object