New: the Sitejar partner program

Integration

Sitejar Asana integration

The Sitejar Asana integration turns website scan findings into Asana tasks in the project 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 completion 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 Asana 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 completion, read back from Asana, shows on the finding.
  • A default project for the workspace, and its own project 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 Asana integration is for

Teams that already plan their work in Asana and want website problems in the same queue as everything else. If your team runs web work in Asana projects, findings arrive as Asana tasks you can assign, date and move through sections like any other task. 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 Asana

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 project

Give a site its own destination, and its findings go to that project 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 Asana to Sitejar

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

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

How to send findings to Asana

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 Asana" in the bulk actions bar, or choose "Create tasks" and pick Asana under "Send to". Up to 50 at a time.
  2. On one finding, use "Send to Asana" in its Task section, which then links to the task.
  3. On a report, choose "Send report to Asana" 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 Asana, and what it stores

What an Asana 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. Asana stores the body as plain-text notes, so the Markdown markers (asterisks, backticks and the code fence) show as typed. The content is the same.

Permissions Sitejar asks for in Asana

Sitejar connects through Asana's OAuth flow and acts as the Asana user who approved it. It lists workspaces and projects, creates tasks and subtasks, adds comments, reads whether a task is complete and, if you turn it on, marks it complete or incomplete.

Asana access tokens last about an hour. Sitejar renews them with the refresh token and saves the new pair.

What Sitejar stores about your Asana connection

Sitejar stores the Asana access token and refresh token, the name of the Asana user who connected for the card, the destinations you pick, and the last error Asana 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 completion and when it last checked. The one piece of personal data Sitejar keeps from Asana is the name of the user who 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 Asana. To revoke the grant on the Asana side too, remove Sitejar in Asana's own settings.

What happens in Asana 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 completion from Asana, at most once every 10 minutes. The finding shows Open or Completed, from Asana's own completed mark. If Asana answers with an error, the last known completion stays. Tasks deleted in Asana 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 Asana card. Tasks whose finding is not detected then move to complete, and those whose finding comes back move to incomplete. It is off until you turn it on.

Which plans include the Asana integration, and its limits

Asana 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 Asana 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.
  • Projects are offered as Workspace / Project, the first 100 unarchived projects in each workspace.
  • In a whole-report send, the findings are subtasks of the report task rather than separate tasks in the project.
  • Dedupe belongs to the connection: findings sent through a connection you have since replaced go out as new tasks.

Troubleshooting the Asana integration

"That connection link expired or was already used"

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

"Choose where Asana 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 Asana

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

The task body shows asterisks and backticks

That is expected. Asana task notes are plain text, so the Markdown Sitejar writes appears as typed. Nothing is missing.

A project is missing from "Tasks go to"

Archived projects are not offered, and only the first 100 projects in each workspace are listed. Unarchive the project, or check that the Asana user who connected can see it.

Asana integration FAQ

Does sending a finding to Asana 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 Asana task mark the finding fixed in Sitejar?

No. Sitejar shows the task's completion, 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 Asana?

The credentials for the connection, encrypted with AES-256-GCM, the name of the Asana user who connected, and for each task it created, its id, url and last known completion. Disconnecting deletes the credentials at once.

Which plan do I need for the Asana integration?

Asana 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.

Where do the tasks from a whole-report send appear in Asana?

Sitejar creates one task for the report in the project you chose, and each finding becomes a subtask of it. Open the report task to see them.

Last updated . Asana and the Asana logo are trademarks of Asana, Inc. Sitejar is not affiliated with or endorsed by Asana, Inc.