New: the Sitejar partner program

Integration

Sitejar ClickUp integration

The Sitejar ClickUp integration turns website scan findings into ClickUp tasks in the list you choose, one task per finding and never a duplicate: sending a finding again adds a comment to the task it already has. Each task carries the rule, the severity, the pages it was found on and the suggested fix, its status shows on the finding in Sitejar, and only a scan that no longer detects the problem marks it fixed.

On Agency and above.

What the Sitejar ClickUp integration does

Sitejar scans a site in a real browser for accessibility (WCAG 2.1 AA), security, privacy, deceptive design, technical quality and SEO, and tracks each problem from scan to scan. This integration carries those findings to where your team plans its work, written so whoever picks one up can start without opening Sitejar.

  • One task per finding. Sending it again adds a comment instead of a second task.
  • The task's status, read back from ClickUp, shows on the finding.
  • A default list for the workspace, and its own list for any site that needs one.
  • Whole reports in one send: one parent task for the report, with each finding as a subtask.

Who the ClickUp integration is for

Teams that already plan their work in ClickUp and want website problems in the same queue as everything else. If your team plans in ClickUp spaces and lists, findings arrive as ClickUp tasks with your list's statuses, ready to assign and prioritize. It suits agencies handing client fixes to a delivery team, and developers who would rather get a task with a selector and a fix than a PDF.

Send accessibility issues to ClickUp

Accessibility is the most common reason teams send findings, but any finding can go: a missing security header, a tracker that loads before consent, a broken link.

Turn a new scan into a backlog

Send a whole report and Sitejar creates one parent task for the report, with each finding as a subtask, most severe first, filtered by severity and with or without Needs review findings. Send the same report again later and only the findings not yet sent are added.

Send just what fits this sprint

Select a handful of findings on the Findings page, or open one finding, and send only those. The rest stay in Sitejar until you are ready.

Keep each client's work in its own list

Give a site its own destination, and its findings go to that list while everything else goes to the default. On Agency Plus, a client can have a destination too: a site's own wins over its client's, and its client's over the default.

How to connect ClickUp to Sitejar

  1. Sign in to Sitejar as an Owner or Admin of the workspace and open Settings, then Integrations.
  2. On the ClickUp card, choose "Connect ClickUp". If your plan does not include ClickUp, the card says "Not on your plan" instead.
  3. ClickUp opens its own authorization page. Approve access for your ClickUp workspace.
  4. Back in Sitejar, the card says "Connected to" followed by the ClickUp username of the account that connected. Under "Tasks go to", choose the list new tasks go to by default.
  5. Optional: under "Give a site its own destination", pick a site and a list, then choose "Add".

A workspace has one ClickUp connection, and connecting again replaces it.

How to send findings to ClickUp

Anyone whose role can manage findings (Owner, Admin or Editor) can send them, three ways:

  1. On the Findings page, select findings and choose "Send to ClickUp" in the bulk actions bar, or choose "Create tasks" and pick ClickUp under "Send to". Up to 50 at a time.
  2. On one finding, use "Send to ClickUp" in its Task section, which then links to the task.
  3. On a report, choose "Send report to ClickUp" in the Next steps panel ("Send report to a task tool" when more than one is connected), pick the severities, and send. Up to 100 tasks at a time.

What Sitejar sends to ClickUp, and what it stores

What a ClickUp task from Sitejar contains

The title names the dimension, the severity, the rule, the page count and the site: [Accessibility][High] Form field missing a label (12 pages) | example.com.

The body carries the confidence label (Confirmed, Likely or Needs review), how many instances on how many pages and the scan date, a CSS selector, the WCAG success criterion where one applies, the first 20 page urls, the suggested fix and its code when one exists (or "No AI fix yet"), and a link back to the finding. It never contains evidence captured from your pages or their content. ClickUp takes the body as a Markdown description, so the selector and any suggested code read as code.

Permissions Sitejar asks for in ClickUp

ClickUp's OAuth does not split access into scopes. The connection acts as the ClickUp user who approved it, in the workspaces that user authorized. Sitejar uses it to list spaces and lists, create tasks and subtasks, comment, read a task's status and, if you turn it on, change it.

What Sitejar stores about your ClickUp connection

Sitejar stores the ClickUp access token, the ClickUp username of the account that connected for the card, the destinations you pick, and the last error ClickUp returned. Credentials are encrypted with AES-256-GCM and never sent to your browser. For each task it created, Sitejar keeps the task's id, url, last status and when it last checked. The one piece of personal data Sitejar keeps from ClickUp is the username of the account that approved access, shown on the card so you know whose access it is.

Disconnecting empties the stored credentials at once, and the tasks already created stay in ClickUp. To revoke the grant on the ClickUp side too, remove Sitejar in ClickUp's own settings.

What happens in ClickUp after the next scan

The sync runs one way: a scan can move a task, but closing a task never marks a finding fixed. Only a scan that no longer detects the problem does, so a task closed by mistake or before the deploy cannot flatter your scores.

When a linked task is shown in Sitejar, Sitejar reads its status from ClickUp, at most once every 10 minutes. The finding shows the task's status by name and treats it as closed when ClickUp says the status type is closed or done. If ClickUp answers with an error, the last known status stays. Tasks deleted in ClickUp show as Removed, and one closed while the latest scan still finds the problem shows "Reopened: closed in the tool, still detected in the latest scan."

On Business and above, each completed scan adds one comment to every linked task: "Still detected in the Sitejar scan of 3 November 2026." or "Not detected in the Sitejar scan of 3 November 2026. A scan, not this task, confirms a fix."

On Agency Plus, you can turn on "Move tasks after each scan" on the ClickUp card. Tasks whose finding is not detected then move to the list's first status of type closed or done, and those whose finding comes back move to the list's first open status. It is off until you turn it on.

Which plans include the ClickUp integration, and its limits

ClickUp is on Agency and above. Whole-report sends and after-scan comments are on Business and above, and automatic moves and per-client destinations are on Agency Plus. To see everything each plan includes, compare plans on the pricing page.

  • One ClickUp connection per workspace.
  • Up to 50 findings per send from the findings list, and up to 100 tasks per whole-report send. Send the report again for the rest.
  • Lists are offered as Space / List across your spaces, up to 200, and archived spaces and lists are left out.
  • Dedupe belongs to the connection: findings sent through a connection you have since replaced go out as new tasks.

Troubleshooting the ClickUp integration

"That connection link expired or was already used"

The link ClickUp sends you back with works once, within 10 minutes of choosing Connect. Choose "Connect ClickUp" again and finish without a long pause.

"Choose where ClickUp tasks go for this site first"

No destination applies to that site yet. Choose a default under "Tasks go to", or give the site its own.

The card shows "Last attempt" with an error from ClickUp

That is what ClickUp answered on the last call. "ClickUp answered 401" or "403" usually means the access was revoked or the connected account lost access to that list: connect again, or choose another list. "ClickUp answered 404" usually means it was deleted.

Moving tasks fails with "The ClickUp list has no matching status"

Automatic moves need the list to have a status of type closed or done, and one of type open to reopen. Check the list's statuses in ClickUp, or turn "Move tasks after each scan" off.

A list is missing from "Tasks go to"

Archived spaces and lists are not offered, and the list stops at 200. Unarchive the list, or check that the ClickUp user who connected can see it.

ClickUp integration FAQ

Does sending a finding to ClickUp twice create two tasks?

No. Sitejar links each finding to the task it created. Sending the same finding again through the same connection adds a dated comment with its current details to that task.

Does closing the ClickUp task mark the finding fixed in Sitejar?

No. Sitejar shows the task's status, but a finding counts as fixed only when a scan no longer detects the problem. If the task is closed while the latest scan still finds it, the finding says it was reopened.

What does Sitejar store from ClickUp?

The credentials for the connection, encrypted with AES-256-GCM, the ClickUp username of the account that connected, and for each task it created, its id, url and last known status. Disconnecting deletes the credentials at once.

Which plan do I need for the ClickUp integration?

ClickUp is on Agency and above. Whole-report sends and after-scan comments are on Business and above, and moving tasks automatically after a scan is on Agency Plus.

Whose ClickUp account do the tasks come from?

From the ClickUp user who approved access when the integration was connected. The card shows that username. To change it, disconnect and connect again while signed in to ClickUp as the other user.

Last updated . ClickUp and the ClickUp logo are trademarks of Mango Technologies, Inc. (ClickUp). Sitejar is not affiliated with or endorsed by Mango Technologies, Inc. (ClickUp).