ClickUp integration

Connecting ClickUp links one of your apps to a specific list. From then on, every report submitted from that app automatically creates a task in that list, with the description, screenshots, and classification. You authorize through ClickUp's OAuth screen.

You can connect more than one tracker to the same app; each report fans out to every connected integration independently.

• You've created an app in the BugScreen console.
• You can sign in to a ClickUp account with access to the workspace and list you want tasks created in. We recommend a dedicated member owned by your team rather than a personal one — see below.

We recommend authorizing BugScreen with a dedicated ClickUp member owned by your team, rather than with a personal one. ClickUp has no separate bot or app identity for creating tasks, so a dedicated member is the only way to keep tasks off an individual's name. It takes a few minutes and avoids two problems.

Tasks are attributed to whoever authorized. ClickUp records that member as the creator of every task BugScreen opens — so it's your name on each one.

The connection outlives staff changes. The token BugScreen holds belongs to that member, so deactivating it — when someone leaves — stops task creation until you reconnect.

Setting one up

1. Invite a new ClickUp member on an address your team controls — for example [email protected].
2. Set its display name to BugScreen, so created tasks are clearly attributed.
3. Give it access to the space and list you plan to connect, with permission to create tasks there.
4. Sign out of ClickUp and back in as that member — or use a private window — then follow the connect steps below. The authorization screen reuses whichever ClickUp session your browser already has, so it won't offer you an account picker.

This uses one ClickUp seat.

1. Open your app in the console and go to the Integrations section.
2. Click Connect ClickUp. You'll be redirected to ClickUp to authorize BugScreen and choose which workspace to grant access to.
3. Approve the authorization. You'll be returned to the console.
4. Drill into the workspace, then space, then list tasks should be created in, and finalize.

Each report creates a ClickUp task in your chosen list containing:

• A name derived from the report and a Markdown description.
• Screenshots and logs uploaded as attachments on the task.
• An optional initial status, if the list defines one you selected.

Priority & tags

• Severity maps to ClickUp's built-in priority — high, medium, or low.
• Every task is tagged bugscreen and bug, plus type:<value> and severity:<value> from the reporter's classification.

After connecting, use Test on the integration to confirm everything works end to end. The test creates a real sample task and shows you whether it succeeded.

To file into a different workspace, space, or list, disconnect the ClickUp integration and connect again with the new destination. Disconnecting stops task creation for that app.

If a test or real report fails to create a task, check the following:

• The list was archived or deleted. Reconnect and pick a live list.
• The initial status was renamed or removed. BugScreen retries without the status so the task is still created; reconnect to pick a valid status.
• BugScreen lost access to the workspace — or the member was deactivated. A common cause is that the person who connected ClickUp left and their member was deactivated, taking the token with it. Reconnect to re-authorize — ideally with a dedicated member.
• Connect is blocked with a plan-limit message. Your plan's integration limit has been reached — remove an unused integration or upgrade your plan.