INTEGRATIONS
tapko.app integrations
Your client clicks on the broken thing and types a sentence. It arrives in the tool your team already works in — as a task, a card, a row or a message, with the screenshot attached and the page, browser and viewport one click away. Seven integrations, included on every plan.
Why the destination matters
Most feedback tools are judged on how good their inbox is. That is the wrong test. A report that is filed perfectly in a tool nobody opens during a launch week is worth less than a scruffy one that lands where your developers are already looking.
So tapko.app does not ask your team to adopt another board. The widget does the structuring — page URL, click position, browser, operating system, viewport, breakpoint, screenshot, console logs — and the integration puts the finished report wherever your team already triages work.
Which one you pick is a question about your team's habits, not about features. Every integration carries the same captured context; they differ only in the shape it arrives as.
Pick where client feedback should land
Project management
tapko.app + ClickUp
A ClickUp task in the list you chose
The task carries the report title, the client’s own words and the screenshot, with console logs attached when the widget captured them. Each project points at its own list.
Communication
tapko.app + Slack
A message in the channel you picked
The report is in your channel seconds after it is made — screenshot visible, page named, technical context one click away. Nobody has to be watching a dashboard for it to be seen.
Development
tapko.app + Jira
A Jira issue in your project
The issue arrives with the screenshot attached and the full technical context one click away. Your client never needs a Jira licence to file it.
Project management
tapko.app + Trello
A card in your list
The screenshot becomes the card cover, so a week of client feedback can be triaged from the board view without opening a single card.
Project management
tapko.app + Asana
A task in your Asana project
The task is specific enough to assign and give a due date the moment it appears, without a single follow-up question to the client.
Documentation
tapko.app + Notion
A row in your database
The screenshot is embedded and the properties are already filled in, so the filters, views and rollups you have built keep working on client feedback too.
Automation
tapko.app + Zapier
A Zap you build yourself
Every report can fire a Zap carrying the screenshot, the page, the browser and the client’s own words into any of the 6,000+ apps Zapier connects to.
What every integration carries
| Captured on every report | Where you get it |
|---|---|
| Report title and the client's own words | In the task, card, row or message itself |
| Screenshot of the page as the client saw it | Attached, embedded or set as the cover |
| Console logs, when the widget captured them | Attached alongside the screenshot |
| Exact page URL and where on it the client clicked | One click away, on the linked tapko.app record |
| Browser, operating system and user agent | One click away, on the linked tapko.app record |
| Viewport size and breakpoint | One click away, on the linked tapko.app record |
The link runs both ways, so the full technical context is always one click from whichever side your team happens to be working on.
Choosing between them
If your developers live on a board — ClickUp, Jira, Trello or Asana. The report becomes a unit of work you can assign, prioritise and close, which is what you want when the feedback arrives in volume during a build.
If the problem is that nobody notices in time — Slack. A board integration files the report; Slack tells somebody it exists. Agencies running a launch week often want both.
If feedback has to sit next to your documentation — Notion. The report becomes a row with real properties, so the views and rollups you have already built apply to it.
If your tool is not on this list — Zapier. The same structured report, routed into any of the 6,000+ apps Zapier reaches.
Nothing here is exclusive. Connections are made per account and destinations are chosen per project, so a client build can post to Slack while the work itself lives on a ClickUp list.
Frequently asked questions
Which tools does tapko.app integrate with?
ClickUp, Slack, Jira, Trello, Asana, Notion and Zapier. The first six send client feedback straight into that tool; Zapier is the route to anything else, carrying the same report into any of the 6,000+ apps it connects to.
Do the integrations cost extra?
No. Every integration is included on every tapko.app plan, including the free plan, which covers one project with no credit card and no expiry. There is no integrations add-on and no per-connection charge.
Does my client need an account in the tool I connect?
No. Your client never touches the connected tool — no seat, no licence, no tapko.app account and no browser extension. They click on the page where they see the problem and type a comment. The task, card, row or message appears on your side.
Can different projects send feedback to different places?
Yes. A connection is authorised once for your account, and the destination — the list, board, channel, project or database — is chosen per tapko.app project. One client's reports never land on another client's board.
What ends up in the connected tool?
The report title, the client's own description and the screenshot, plus console logs when the widget captured them. Everything is linked 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 captured at the moment of the report.
What if the tool we use is not on the list?
Use Zapier. It carries the same structured report — screenshot, page, browser and the client's words — into any of the 6,000+ apps Zapier connects to, which covers the tools we have not built a native integration for yet.