INTEGRATION
tapko.app + GitHub
A client comment becomes a GitHub issue your developers can pick up. It runs through Zapier today, because I haven't built a native GitHub app yet.
Who this is for
Your client comments on the page. Your developers work from GitHub. Someone ends up copying comments across by hand.
With a Zap, each new comment creates an issue with the screenshot link and page URL already in it. The client never sees GitHub.
Setting it up
- Open Plugins in your tapko.app account and connect Zapier.
- In Zapier, start a Zap with tapko.app as the trigger and choose a new report, for one client project.
- Add GitHub as the action, choose Create Issue, and map the comment, screenshot link and page URL.
What this doesn't do
It is one way. Closing a GitHub issue doesn't mark the comment resolved in tapko.app. You can build that with a second Zap on the status change, but it isn't built in.
If you want a connection without Zapier, tell me and I'll count it toward a native app.
Frequently asked questions
Is there a native GitHub integration?
Not yet, as of Oct 2026. GitHub issues work through Zapier today. A native connection is on the list but has no date.
What goes into the GitHub issue?
Whatever you map in the Zap. The trigger carries the client comment, a link to the screenshot, the page URL, the click position, priority and status. Most setups put the comment in the title and the rest in the body.
Does my client need a GitHub account?
No. They comment on the page and never see GitHub. The issue is for your developers.
Can different clients go to different repositories?
Yes. Each Zap watches one tapko.app project, so you point each client project at its own repository.
Does this cost extra?
Not on the tapko.app side. A free Zapier plan runs single-step Zaps, which covers one issue per comment. Filters and branching need a paid Zapier plan, and that is Zapier's pricing.