--- updatedAt: 2026-08-27T14:49:25.000Z agentTools: projectIndex: https://docs.socket.dev/llms.txt --- # ClickUp Integration Connect your ClickUp Workspace to Socket to create and manage ClickUp tasks from alerts, with manual creation and automated ticketing rules. The ClickUp integration is currently in **Beta** and is available on **Business** and **Enterprise** plans. Connect your ClickUp Workspace to Socket to create and manage ClickUp tasks directly from Socket alerts. Create tasks manually from individual alerts, or set up automated ticketing rules that create and update ClickUp tasks based on alert events in your organization. The integration connects to ClickUp using OAuth. Authorization happens entirely from the Socket dashboard β€” there is no separate app to install in a third-party admin console. ### Key capabilities * **Manual task creation** β€” Create a ClickUp task from alerts in the Socket dashboard. * **Automated ticketing rules** β€” Define rules that automatically create ClickUp tasks when specific alert events occur, with configurable conditions, List, priority, tags, and assignee. * **Two-way sync** β€” When linked ClickUp tasks are updated, completed, or deleted, Socket is notified and can update the alert accordingly. * **Multi-workspace support** β€” Connect more than one ClickUp Workspace to a single Socket organization. ## Prerequisites * Confirm your Socket account is on a **Business** or **Enterprise** plan. * Have a ClickUp Workspace ready, with permission to authorize apps for the Workspace (and access to the Spaces/Lists) you want to connect. * Hold an **Owner** or **Admin** role in your Socket organization (required to connect and disconnect the integration). ## Connect ClickUp to Socket ### Step 1: Open the ClickUp integration page In the Socket dashboard, go to **Settings β†’ Integrations β†’ ClickUp** for your organization, then click **Connect**. A dialog opens with step-by-step instructions and an installation link. ### Step 2: Start the authorization 1. Click **Install** to open the ClickUp authorization window. 2. If the authorization window does not open, your browser may be blocking popups. Allow popups for this site, or copy the installation link shown in the dialog and open it in a new browser tab. ### Step 3: Approve access in ClickUp In the ClickUp authorization window: 1. Select the **Workspace** you want Socket to use. 2. Review the requested access and approve the connection. ClickUp OAuth does not use granular scopes. Socket receives access to the Workspaces you approve, limited to what the authorizing ClickUp user can already do in those Workspaces. Tip: If you want to connect multiple Workspaces, authorize one Workspace per connection (repeat **Connect** for each Workspace) so Lists and webhooks stay scoped to the intended Workspace. ### Step 4: Verify the connection After you authorize, the Socket dashboard reloads automatically and the connection appears under **Settings β†’ Integrations β†’ ClickUp** with a **Connected** status badge, including the Workspace name, who connected it, and when. Tip: To connect additional ClickUp Workspaces, repeat the steps above. ## Disconnect ClickUp To disconnect a ClickUp Workspace from your Socket organization: 1. Go to **Settings β†’ Integrations β†’ ClickUp** in the Socket dashboard. 2. Find the ClickUp connection you want to remove. 3. Click the button with the 3 dots, and select **Disconnect...**, then confirm. This removes the link between the ClickUp Workspace and your Socket organization. Existing tasks in ClickUp are **not** deleted or modified. Alternatively, a ClickUp admin can revoke the connection in the ClickUp Workspace settings. If a connection shows an **Error** or **revoked** status, remove the connection and create a new one to restore access. ## Create ClickUp tasks from alerts Once the integration is connected, you can create ClickUp tasks directly from alerts in the Socket dashboard. 1. Open an alert in the Socket dashboard. 2. Click the **Create Ticket** button. 3. Select the ClickUp connection and **List**, then fill in any additional fields (priority, tags, assignee). 4. Submit to create the task. Lists are shown as `Space / List` or `Space / Folder / List` so you can tell similarly named Lists apart. The created task is linked to the alert, and a link to the ClickUp task appears on the alert so you can navigate directly to it. ## Automated ticketing rules Automated ticketing rules let you define conditions under which ClickUp tasks are automatically created and updated. Configure these rules from **Settings β†’ Integrations β†’ Ticketing** in the Socket dashboard. Ticketing is available on **Business** and **Enterprise** plans. ### Create a ticketing rule Click **Create Configuration** to start the wizard: #### 1. Select events Choose which events should trigger the rule. #### 2. Select conditions Optionally define conditions to filter which alerts match this rule, targeting specific alert types, priority levels, repositories, or other attributes. #### 3. Select project Choose the ClickUp connection and where tasks should be created: * **Integration** β€” Select which connected ClickUp Workspace to use. * **List** β€” Search and select the ClickUp List where tasks will be created. #### 4. Configure issue Define how the ClickUp task should be created: * **Priority** β€” Set a specific priority (**Urgent**, **High**, **Normal**, or **Low**), or use **Auto** to map the alert priority to a ClickUp priority automatically. * **Labels** β€” Optionally add ClickUp tags to created tasks. * **Assignee** β€” Optionally assign the task to a ClickUp user (search by name). Select a List first so Socket can load that List’s members. Note: ClickUp does not use issue types. Additional fields under Advanced settings are not supported for ClickUp. #### 5. Configure actions Define what happens when alert state changes: * **Create issue** β€” Automatically create a new ClickUp task when the rule conditions are met. * **Update issue** β€” Update the linked ClickUp task when the alert is updated. Optionally change the ClickUp task status when the alert is cleared in Socket. * **Mark alert as "ignored" when ticket is closed** β€” Optionally triage-ignore the Socket alert when the linked ClickUp task is closed or completed. After reviewing the summary, click **Create** to activate the rule. ## Permissions ### Socket roles | Role | Capabilities | | ----------- | ---------------------------------------------- | | Owner | Connect, disconnect, configure ticketing rules | | Admin | Connect, disconnect, configure ticketing rules | | Member | View connections, create tasks from alerts | | Contributor | View connections | ### ClickUp app permissions When you authorize the integration, Socket receives access to the ClickUp Workspaces you approve, using the permissions of the authorizing ClickUp user. Socket uses this access to: * Read Workspace structure (Spaces, Folders, Lists), tags, statuses, priorities, and members * Create and update tasks from alerts and ticketing rules * Register Workspace webhooks so task updates, status changes, and deletions sync back to Socket Socket does not access Workspaces you do not approve during authorization. ## Troubleshooting Only users with **Owner** or **Admin** roles in the Socket organization can connect or disconnect the integration. If you have a different role, ask an administrator to complete the connection. Your browser may be blocking popups. Allow popups for the Socket dashboard, or copy the installation link from the Connect dialog and open it in a new browser tab. The access granted to Socket may have been revoked in ClickUp. Remove the connection in **Settings β†’ Integrations β†’ ClickUp** and connect again. Verify the following: 1. The ticketing rule is set to **Active** status. 2. The ClickUp Workspace is still connected (check **Settings β†’ Integrations β†’ ClickUp**). 3. The alert event matches the rule's event and condition filters. 4. The selected ClickUp List is still valid in your Workspace. 5. The alert is not **monitored** or **ignored**. Socket does not create or update tickets for alerts in those states. If you encounter problems or have questions not explained here, [contact support](https://docs.socket.dev/docs/contact-support). ### Known issues and limitations ClickUp may let you approve more than one Workspace during a single authorization. Socket currently operates against the primary authorized Workspace for that connection (for listing Lists and registering webhooks). To use another Workspace, create a separate connection and authorize only that Workspace. Additional fields under **Advanced settings** in the ticketing configuration have no effect on ClickUp tasks. These fields are not supported for ClickUp. ## Next steps * [Webhooks](https://docs.socket.dev/docs/webhooks) β€” Set up webhooks to receive real-time notifications for alert events. * [Customizable Security Policies](https://docs.socket.dev/docs/enabled-issues) β€” Configure which alert types trigger warnings and blocks across your organization. * [Organization Alerts](https://docs.socket.dev/docs/organization-alerts) β€” Review and manage alerts across all repositories in your organization.