To share ClickUp data with external apps, you can use two kinds of webhooks in ClickUp:

1. Webhooks created through the ClickUp Public API.
2. Webhooks triggered by Automations.

Feature availability and limits vary by plan and user role. Learn more

API webhooks

You should use API webhooks when you want to broadly track all create, update, delete events for tasks, Lists, Folders, Spaces, Goals, and Targets.

Learn more about ClickUp API webhooks including:

• See example payloads.
• Review the specification for the ClickUp Public API webhook endpoints.
• Send your first Create webhook request right from your browser.

Automation webhooks

You should use Automations webhooks when you want complete control over the Triggers and Conditions that send your data to external apps.

There are two kinds of Automation webhooks you can create in ClickUp:

• Task webhooks: Send data when tasks are updated.
• Chat webhooks: Send data when chat messages are posted.

Create a webhook

You'll need to create a webhook for each destination that will receive ClickUp data from Automations.

You can re-use webhooks you've created in Automations throughout your Workspace, but you'll need to configure separate webhooks for Task and Chat Automations.

Make sure you test your webhook before you add it to Automations that will send real data.

Use dynamic variables in your Webhook

Dynamic variables in the URL can help your app efficiently process the data it receives from ClickUp.

You can use dynamic variables in the URL for your webhook, such as the task ID.

Use headers

Headers can include metadata that allows your app to process incoming webhook payloads securely and accurately. By default, ClickUp includes the following header:

Content-type: application/json

Use URL parameters

You can also set URL parameters for each webhook to help your app process data accurately.

Unlike the dynamic variables, URL parameters are static. The values won't change each time your Automation is triggered.

Test webhooks

When you first start using webhooks, we recommend testing your webhooks before you send real data from your ClickUp Workspace.

You can find and use free tools online to test and experiment with webhooks. For example, you can use webhook.site to generate a webhook URL and see the webhook payloads sent from ClickUp.

For API webhooks:

• Filter your first webhook to specific events such as taskCreated and taskUpdated.
• Filter your first webhook to one specific location, such as dedicated List that only contains test tasks with generic but representative data.

For Automation webhooks:

• Apply precise Triggers and Conditions, such as a checkbox Custom Field to control when data is sent.
• Add the Automation to a specific List or Channel first, with generic but representative tasks and messages.