What the Asana integration does
Every new comment on a project you route to Asana becomes a task in the Asana project you choose, with the page, the browser details and a link to the screenshot in its description. Completion syncs both ways: complete the task in Asana and the comment is resolved, resolve the comment in Huddlekit and the task is completed. For an overview, see the Asana integration page.
Before you start
- Plan: Asana is on the Team plan. See Understanding plans and pricing.
- Role: only workspace owners and admins can connect Asana or change its settings. Other members can open Integrations and see that Asana is connected, but can't change anything.
- Asana access: the Asana account you connect with needs access to every Asana project you plan to use.
Connect Asana
- Open Integrations in your workspace sidebar.
- Click Connect on the Asana row.
- Approve Huddlekit on Asana's consent screen.
- You land back on Integrations with the message Asana connected: "Nothing syncs until you pick an Asana project."
Nothing is sent yet. Huddlekit doesn't guess a project for you, so the Asana row shows Not configured until you choose one.
Choose where each project's tasks go
Open the ⋯ menu on the Asana row and choose Configure. The Asana settings dialog opens. Changes save as you make them, so Done just closes it.
- Default Asana project: where comments go from every project you don't set individually, including projects created later. Choose No default if only the projects you set should sync.
- Projects: one row for each website, web app and media project. Leave a row on the default, pick an Asana project of its own, or choose Don't sync to keep that project out of Asana even when a default is set.
Asana projects are listed by Asana team. A connection uses one Asana workspace, and every Asana project you pick has to be in it. You can only switch workspaces while no project or default points at an Asana project.
Changing a project's Asana project only affects new comments. Tasks that already exist stay where they are.
How completion syncs
Asana tasks have no status, only a checkbox for done, and every Asana project names its sections its own way. So Huddlekit syncs completion instead of status:
- Resolve a comment and its task is marked complete. Reopen the comment and the task goes back to incomplete.
- Complete the task in Asana and the comment is resolved. Mark it incomplete and the comment goes back to Open.
- Open, In review and In progress stay in Huddlekit. Moving a task between sections in Asana doesn't change its comment.
A change made in Asana usually reaches Huddlekit within seconds. Completing a task in Asana also reaches your other connected trackers, such as Linear, ClickUp or Notion, just like resolving the comment in Huddlekit would.
What each task includes
- Name: the comment number and the first line of the comment, like
#42 — Logo is blurry on mobile. When several of your projects share the default Asana project, the project name goes in front:[Acme site] #42 — …. - Description: the full comment, the project, who reported it, where it was left, and a link to open the screenshot. Where it was left is a link to the page on a website, and the page number or video time on a media file. Media comments have no screenshot. The screenshot is a link, not an image in the task.
- Environment: OS, browser, resolution, viewport, pixel ratio, color depth and network, whichever were captured. Website comments carry the most. Web app comments carry fewer, and media comments have none.
- Open in Huddlekit: a link back to the comment.
Private comments are sent too, so think about who can see an Asana project before routing a project to it. A new comment usually reaches Asana within about a minute.
What stays in Huddlekit
Completion is the only thing that syncs, and it's the only thing read back from Asana. The task description is written once, when the comment arrives, so later edits to the comment text aren't pushed. Replies, priority, tags, assignees, attachments and due dates stay in Huddlekit, and comments your team adds in Asana stay in Asana.
Comments aren't copied over later if they were left before you connected, before their project had an Asana project, while it was set to Don't sync, or while syncing was paused. If one of them changes status later and its project syncs, it becomes a task then.
Deleting a task in Asana doesn't delete the comment. Its completion just stops syncing.
One-way sync
If you'd rather keep changes made in Asana from coming back, open the ⋯ menu and choose Switch to one-way sync. The option appears once a project or the default has an Asana project. Changes made in Asana then stay in Asana, including during the nightly check. Comments still become tasks, and resolving or reopening a comment still completes or reopens its task. Switch to two-way sync in the same menu turns it back on.
Nightly check
Once a night, Huddlekit compares linked tasks with their comments and fixes completion that drifted, for example after a missed update. If only the task changed, the comment follows it, unless the connection is set to one-way sync. If the comment changed since it last synced, Huddlekit wins, and a comment on the task explains why it was reset. The same check restarts two-way sync if Asana has stopped sending updates.
Disconnecting
Open the ⋯ menu and choose Disconnect. Huddlekit's access to Asana ends and no more comments are sent. Tasks already in Asana stay there.
If you connect the same Asana workspace again later, your project settings come back, and existing tasks keep syncing instead of being created twice.
If your plan changes
Syncing only runs while the workspace is on the Team plan with its payments up to date. If the workspace moves to another plan, or a payment is past due, the Asana row shows Paused and nothing syncs in either direction. Comments left during that time aren't queued up to send later. Your settings are kept, and Disconnect stays available.
Once the workspace is back on Team, the nightly check repairs tasks that already exist, the same way it does any other night.
Troubleshooting
If connecting doesn't finish, you're returned to Integrations with an Asana not connected message and the reason:
- "That Asana account has no workspace." Create or join a workspace in Asana, then connect again.
- "Asana did not grant lasting access. Try again." Click Connect again.
- "Asana refused the access Huddlekit asked for. Contact support." Email support@huddlekit.com and we'll look into it.
- "Cancelled. Nothing changed." You cancelled on Asana's screen. Click Connect again when you're ready.
- "That link expired. Start again." Too much time passed on Asana's screen. Click Connect again.
- "You switched accounts partway. Sign back in and retry." You were signed in to Huddlekit as someone else by the time you came back. Sign in as the admin who started, then connect again.
- "That link was already used. Start again." or "That link was not valid. Start again." Click Connect again from Integrations.
- "Only workspace admins can do this." or "Needs the Team plan." Ask an owner or admin, or upgrade the workspace first.
- Anything ending in "Try again." Click Connect again.
Sync failing on the Asana row means a comment couldn't be sent to Asana and won't be retried. Open Configure from the ⋯ menu and hover over Sync failing for the reason, such as "Asana no longer accepts Huddlekit. Reconnect Asana." It clears once a comment syncs to Asana again.
An Asana project won't save. Huddlekit checks each Asana project with Asana before saving it:
- "That Asana project is archived. Pick another, or unarchive it."
- "Asana could not find that project for your user. It may have been deleted, or not shared with you."
- "That project is not in the chosen Asana workspace."
- "Your Asana user is not in that workspace. Reconnect Asana, or pick another."
- "Asana refused the connection. Reconnect Asana."
Two-way sync delayed or Two-way sync not set up means completions made in Asana aren't coming back yet. New comments still become tasks. Choose Resume two-way sync in the ⋯ menu. If you see "Asana did not accept the webhook. Try again, or Reconnect in the ⋯ menu.", try Reconnect. Your settings are kept as long as you connect the same Asana workspace.