INTEGRATION
tapko.app + Asana
Your client clicks on the broken thing and types a sentence. An Asana task appears in your project with the screenshot attached — already specific enough to assign to someone and give a due date, without a single follow-up question.
The gap this closes
Asana runs the whole agency, not just the engineering half — account managers, designers and project managers all live in it. Which means client feedback has to arrive in a form all of them can act on, not just the developer who knows what a user agent string is.
In practice it does the opposite. Feedback arrives as “the client says the contact form is broken” in a project manager's inbox, gets turned into a task with exactly that sentence in it, and then bounces — assigned to a developer who cannot reproduce it, sent back to the PM, who emails the client, who replies three days later.
The Asana integration removes the bounce. The task is specific when it is created, because the report was structured at the moment the client made it.
What lands in the Asana task
| Captured on every report | Where you get it |
|---|---|
| Report title and the client's own words | Task name and notes |
| Screenshot of the page as the client saw it | Attached to the task |
| Console logs, when the widget captured them | Attached to the task |
| Exact page URL and where on it the client clicked | One click from the task |
| Browser, operating system and user agent | One click from the task |
| Viewport size and breakpoint | One click from the task |
| Priority and status of the report | One click from the task |
The point is that a project manager can assign the task without understanding it. Everything a developer will ask for is already recorded.
Setting it up
1. Authorise Asana. Open Plugins in your tapko.app account and click Connect on Asana. You approve on the Asana consent screen and are returned immediately. No personal access token to generate or store.
2. Choose the project and section. In the project you want to sync, pick the workspace, then the Asana project, then a section if you use them. Each tapko.app project points at its own Asana project, so one client's reports never land in another client's board.
3. Share the project link. Send your client the link. From their next report onwards, tasks appear in the project you chose.
Disconnecting is the same route in reverse — Plugins, Disconnect. The stored authorisation is deleted and syncing stops. Tasks already in Asana stay where they are.
Your client never sees Asana
Asana guest access looks like the obvious answer to client feedback and rarely survives a month. The client sees more of the project than you meant to show, comments land on tasks that are half-finished, and someone on your team ends up maintaining a sanitised second project just for them.
tapko.app asks the client for nothing. No Asana seat, no guest invite, no tapko.app account, no extension. They open the site, click where the problem is, and type. The structured task appears on your side, in the project you already run the work from.
That is what makes it stick. The fewer steps you put between noticing a problem and reporting it, the more problems you hear about — and the ones you never hear about are the expensive ones.
Frequently asked questions
Does my client need an Asana account?
No. Your client never touches Asana. They click on the page where they see the problem and type a comment — no Asana seat, no guest invite, no tapko.app account, no browser extension. The task appears in your project, not theirs.
What ends up in the Asana task?
The task name is the report title and the notes hold the client's own description, with the screenshot attached — and console logs too, when the widget captured them. The task links back to the tapko.app record, which holds the exact page URL, the spot on the page the client clicked, and the browser, operating system, viewport size and breakpoint.
Can tasks be assigned automatically?
Tasks arrive unassigned in the project and section you chose, which is what most teams want — assignment is a triage decision, not something to guess at. Asana's own rules can then take over: auto-assign by section, set a due date, or move the task once someone picks it up.
Can different projects sync to different Asana projects?
Yes. The Asana connection is made once for your account, and the destination project and section are chosen per tapko.app project — so each client's feedback lands in that client's own Asana project.
Does the Asana integration cost extra?
No. Every tapko.app integration — Asana, Slack, Jira, Trello, ClickUp, Notion and Zapier — is included on every plan, including the free plan, which covers one project with no credit card and no expiry.