ClickUp Source Configuration

ClickUp configuration

Create a ClickUp source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Signing Secret values for provider signature. FastHook uses these settings to validate each ClickUp delivery before it enters the routing workflow.

{
  "type": "CLICKUP",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "CLICKUP",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

ClickUp request contract

FastHook computes HMAC-SHA256 hex over the raw body and compares it with x-signature.

ClickUp headers

Preserve x-signature when sending ClickUp test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

ClickUp setup

1. Create a ClickUp webhook with the FastHook Source URL.
2. Paste the ClickUp webhook secret into FastHook.
3. Route by event and task/list identifiers.

ClickUp routing hints

• ClickUp automation commonly branches by task, list, folder, space, assignee, or status changes so project workflows stay attached to the correct workspace object.
• Use the ClickUp task identifier when downstream updates or notifications must remain idempotent across repeated webhook deliveries.

Continue with ClickUp

• ClickUp webhooks documentation
• Source operations and troubleshooting