ClickUp setup guide

Agents keep projects moving: they read, create and update tasks and issues where your team works.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open ClickUp, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

ClickUp can be connected 2 ways. Where there’s a key or token to paste, that’s usually the quickest.

Personal API token

API key.

1. Sign in to ClickUp as the user the agent should act as (a dedicated member keeps its work easy to spot).
2. Click your avatar, open Settings > Apps and click Generate (or Regenerate) under API Token, then Copy. Tokens start with pk_ and never expire.
3. Paste the token into the form.
4. Optional, to start work when a task changes or someone comments: once connected, set up the ClickUp trigger you want on Everdeck's Intake page and copy the address it gives you. ClickUp makes webhooks only through its API, so run this with your Workspace ID (the number after app.clickup.com/ in your browser's address bar), your token and that address: curl -X POST https://api.clickup.com/api/v2/team/WORKSPACE_ID/webhook -H "Authorization: YOUR_TOKEN" -H "Content-Type: application/json" -d '{"endpoint": "ADDRESS", "events": ["taskCreated", "taskUpdated", "taskMoved", "taskStatusUpdated", "taskAssigneeUpdated", "taskPriorityUpdated", "taskDueDateUpdated"]}' (for new comments use "events": ["taskCommentPosted"]). Copy the secret in ClickUp's answer into this connection's Webhook secret field, or leave the field empty and Everdeck reads it from ClickUp. Make one webhook per trigger.

Field	What to enter
Personal API token	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.
Webhook secret (optional, only for live updates)	A secret: Everdeck saves it encrypted and never shows it again. The secret ClickUp answered with when the webhook for Everdeck was made. Everdeck accepts only deliveries signed with it. Leave it empty to have Everdeck read it from ClickUp; for several webhooks, separate their secrets with spaces.

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at ClickUp until you delete or rotate it there.

Your ClickUp OAuth app

Your OAuth app.

This way signs in with an OAuth app you create for ClickUp, as its steps describe: Everdeck never uses an app of its own. Register this redirect URI with your app:

https://everdeck.io/api/oauth/callback

Then save the app’s client ID and secret in Everdeck, on the connect page or under OAuth apps, and sign in.

1. As a Workspace owner or admin, click your avatar in ClickUp, open Settings > Apps and click Create new app.
2. Name the app and add the redirect URL https://everdeck.io/api/oauth/callback.
3. Copy the client ID and secret into the form, then choose which Workspaces to authorize.
4. Optional, to start work when a task changes or someone comments: once connected, set up the ClickUp trigger you want on Everdeck's Intake page and copy the address it gives you. ClickUp makes webhooks only through its API: the ClickUp user who signed in creates one with their personal API token (Settings > Apps > API Token) as the Personal API token way of connecting describes, and its secret goes in this connection's Webhook secret field. Make one webhook per trigger.

Field	What to enter
Webhook secret (optional, only for live updates)	A secret: Everdeck saves it encrypted and never shows it again. The secret ClickUp answered with when the webhook for Everdeck was made. Everdeck accepts only deliveries signed with it. Leave it empty to have Everdeck read it from ClickUp; for several webhooks, separate their secrets with spaces.

Disconnecting deletes the tokens Everdeck saved. ClickUp has no token revocation API: remove the app under Settings > Apps.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• List Workspaces and membersTier 0 · ReadReads outside contentclickup_list_workspaces

  List the Workspaces this connection may use, with their members' user ids, names and emails (use the ids as assignees). ClickUp's API calls a Workspace a "team".

• List SpacesTier 0 · ReadReads outside contentclickup_list_spaces

  List the Spaces in a Workspace with their task statuses.

• List Folders and their ListsTier 0 · ReadReads outside contentclickup_list_folders

  List the Folders in a Space, each with its Lists. Lists hold tasks.

• List Lists outside FoldersTier 0 · ReadReads outside contentclickup_list_folderless_lists

  List the Lists that sit directly in a Space, outside any Folder.

• List tasks in a ListTier 0 · ReadReads outside contentclickup_list_tasks

  List the tasks in a List, most recently updated first, 100 per page. Closed tasks are left out unless include_closed is true.

• Find tasks across the WorkspaceTier 0 · ReadReads outside contentclickup_filter_tasks

  Find tasks anywhere in a Workspace by status, assignee, Space, List or update time, most recently updated first, 100 per page. The ClickUp API has no free-text task search.

• Read a taskTier 0 · ReadReads outside contentclickup_get_task

  Read one task: Markdown description, status, assignees, priority, dates, tags, location, subtasks, checklists and custom fields.

• Read commentsTier 0 · ReadReads outside contentclickup_list_comments

  Read a task's comments, newest first (25 at a time). For older ones pass the date and id of the last comment you received.

• Create a taskTier 2 · ReversibleReads outside contentclickup_create_task

  Create a task in a List. Assignees are user ids from list_workspaces; status must be one of the List's statuses; dates are Unix milliseconds.

• Update a taskTier 2 · ReversibleReads outside contentclickup_update_task

  Change a task: name, description, status (to move it through the workflow), priority, dates, or assignees (add and remove lists of user ids). Send only what changes. archived true archives the task (reversible).

• Comment on a taskTier 2 · Reversibleclickup_add_comment

  Add a comment to a task. Assignees and watchers are notified; anyone the task is shared with (including guests) can read it.

What can start work

These events from ClickUp can become tasks for your agents through Intake. How Intake works.

A task was created, updated, moved, or had its status, assignees, priority or due date changed (taskCreated, taskUpdated, taskStatusUpdated, taskAssigneeUpdated, ...).

Connect ClickUp first. Then, on the Intake page, open Webhooks and sources, find the connection under Connections without an address yet and select Get its URL. Give that address to ClickUp as the setup steps above describe: Everdeck shows it only once. Then, on the Rules tab, select New rule to say which requests become tasks and who gets them.

A comment was posted on a task (taskCommentPosted).

Connect ClickUp first. Then, on the Intake page, open Webhooks and sources, find the connection under Connections without an address yet and select Get its URL. Give that address to ClickUp as the setup steps above describe: Everdeck shows it only once. Then, on the Rules tab, select New rule to say which requests become tasks and who gets them.

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If ClickUp later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit or Reconnect.

To stop agents using ClickUp, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.