INTEGRATION
tapko.app + Slack
Your client clicks on the broken thing and types a sentence. Seconds later it is in your channel — screenshot visible, page named, technical context one click away. Nobody has to be watching a dashboard for it to be seen.
The gap this closes
Feedback tools have a quiet failure mode: the report is filed correctly and then nobody looks. It sits in a queue that someone is supposed to check, and on the week it matters most — the week before launch — nobody checks it, because everyone is heads-down building.
Agencies solve this by living in Slack. That is where the standup happens, where the client escalation lands, where someone notices at 6pm that a form is broken. A feedback queue that does not reach Slack is a feedback queue that gets read late.
The Slack integration closes the delay between a client noticing something and your team knowing about it. No polling, no daily digest, no “did anyone see the feedback board today”.
What lands in the Slack message
| Captured on every report | Where you get it |
|---|---|
| Report title and the client's own words | In the message body |
| Screenshot of the page as the client saw it | Previewed in the message |
| Which page the report was made on | In the message body |
| Priority the report came in at | In the message body |
| Where on the page the client clicked | One click from the message |
| Browser, operating system and user agent | One click from the message |
| Viewport size and breakpoint | One click from the message |
| Console logs, when the widget captured them | One click from the message |
The message is deliberately short. Enough to judge whether it is urgent without opening anything, and one click to the full record when it is.
Setting it up
1. Authorise Slack. Open Plugins in your tapko.app account and click Connect on Slack. Slack asks which workspace to install into, you approve, and you are returned immediately. No webhook URL to generate, paste, or rotate.
2. Choose the channel. In the project you want to route, pick the channel its reports should post into. Each tapko.app project posts to its own channel, so one client's bugs never turn up in another client's thread.
3. Share the project link. Send your client the link. From their next report onwards, messages appear in the channel you chose, seconds after they hit submit.
Disconnecting is the same route in reverse — Plugins, Disconnect. The stored authorisation is deleted and posting stops. Messages already in Slack stay where they are.
Slack is for noticing, not for tracking
It is worth being honest about what a channel is good at. Slack is unbeatable at getting something in front of people fast. It is terrible as a system of record — a report posted on Tuesday is unfindable by Thursday, and “it's in the channel somewhere” is how bugs get shipped to production.
So use both. Point the project at a Slack channel so the team hears about it, and at ClickUp, Jira, Trello, Asana or Notion so it is still there next week. One report, both destinations, no duplicate typing.
And either way your client stays out of it. No Slack seat, no guest invite, no tapko.app account, no extension. They click where the problem is and type. Everything else happens on your side.
Frequently asked questions
Does my client need a Slack account?
No. Your client never touches Slack. They click on the page where they see the problem and type a sentence — no Slack seat, no guest invite, no tapko.app account, no browser extension. The message appears in your workspace, not theirs.
What does the Slack message contain?
The report title, the client's own description, the page it happened on and the screenshot, so the message is readable without leaving Slack. A link on the message opens the full tapko.app record, which holds the exact spot on the page the client clicked plus browser, operating system, viewport size and breakpoint.
Will this flood my channel?
Each project posts to the channel you pick for it, so a busy launch week stays contained in that client's channel rather than spilling into general. Most agencies create one channel per active client build and archive it when the site goes live.
Can I use Slack alongside a project management integration?
Yes, and most teams do. Slack is where the team hears about a report; ClickUp, Jira, Trello, Asana or Notion is where it gets tracked. A single report can post to Slack and create a task at the same time.
Does the Slack integration cost extra?
No. Every tapko.app integration — Slack, ClickUp, Jira, Trello, Asana, Notion and Zapier — is included on every plan, including the free plan, which covers one project with no credit card and no expiry.