INTEGRATION
tapko.app + Notion
Your client clicks on the broken thing and types a sentence. A row appears in your database with the screenshot embedded and the properties already filled in — so your existing filters, views and rollups just work on it.
The gap this closes
Plenty of agencies run everything out of Notion — the client wiki, the scope document, the launch checklist and a feedback database somebody set up in the first week of the project. The database is usually well designed. The problem is that it only ever gets populated by hand.
So it drifts. Half the reports are in it, the other half are in an email thread, and by the end of the build nobody trusts the view enough to run a launch meeting off it. A tracker that is only as complete as the last person who remembered to fill it in is not a tracker.
The Notion integration makes the database self-populating. Every report lands as a row with real properties, which means the filtered views you already built start reflecting the actual state of the project.
What lands in the Notion database
| Captured on every report | Where you get it |
|---|---|
| Report title and the client's own words | Page title and body |
| Screenshot of the page as the client saw it | Embedded in the page |
| Exact page URL the report was made on | A database property |
| Priority the report came in at | A database property |
| Status of the report | A database property |
| Browser, operating system and user agent | One click from the page |
| Viewport size, breakpoint and click position | One click from the page |
| Console logs, when the widget captured them | One click from the page |
Properties rather than plain text is the whole point. A row you can filter by page and sort by priority is a tracker; a row of pasted text is a note.
Setting it up
1. Authorise Notion. Open Plugins in your tapko.app account and click Connect on Notion. Notion asks which pages to grant access to — select the page or database that holds your feedback tracker, and nothing else in the workspace is ever readable.
2. Choose the database. In the project you want to sync, pick the database new reports should be created in. Each tapko.app project points at its own database, so one client's reports never appear in another client's view.
3. Share the project link. Send your client the link. From their next report onwards, rows appear in the database you chose.
Disconnecting is the same route in reverse — Plugins, Disconnect. The stored authorisation is deleted and syncing stops. Pages already in Notion stay where they are, with their properties intact.
Your client never sees your workspace
Sharing a Notion page with a client is easy, which is exactly the problem. One shared parent page and they can reach the meeting notes, the estimate you revised twice, and the internal doc about the last project that went badly. Agencies that try it usually end up maintaining a separate client-facing workspace, by hand, forever.
tapko.app keeps the workspace yours. The client gets a link to their own site with a widget on it — no Notion account, no workspace invite, no tapko.app account, no extension. They click where the problem is and type. The row appears on your side.
And the permission runs the other way too: tapko.app only ever sees the pages you handed it during authorisation. One database in, nothing else visible.
Frequently asked questions
Does my client need a Notion account?
No. Your client never touches Notion. They click on the page where they see the problem and type a comment — no Notion account, no workspace invite, no tapko.app account, no browser extension. The row appears in your database, not theirs.
What ends up in the Notion page?
The page title is the report title, the body holds the client's own description with the screenshot embedded, and the page URL, priority and status arrive as database properties you can filter and sort on. A link on the page opens the full tapko.app record with the click position and the browser, operating system, viewport size and breakpoint.
Can I add my own properties to the database?
Yes. tapko.app writes the properties it owns and leaves everything else alone, so your own columns — owner, sprint, billable, client-visible — keep working exactly as they did. Rollups, formulas and linked relations on the database are untouched.
How much of my Notion workspace can tapko.app see?
Only the pages you explicitly select during the Notion authorisation step. Notion's permission model is per-page rather than workspace-wide, so an integration granted access to one feedback database cannot read your client contracts, your internal wiki, or anything else.
Does the Notion integration cost extra?
No. Every tapko.app integration — Notion, Slack, Jira, Trello, Asana, ClickUp and Zapier — is included on every plan, including the free plan, which covers one project with no credit card and no expiry.