INTEGRATION
tapko.app + Zapier
Every client 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. This is the integration for the tool we have not built a native one for yet.
The gap this closes
No feedback tool will ever connect natively to every system an agency runs. Somebody is on Linear, somebody else built their whole reporting layer on Airtable, and somebody has a client who insists everything goes into a shared Google Sheet because that is what their finance team reads.
The usual answer is “it's on the roadmap”, which means the agency exports a CSV once a week until they stop bothering.
Zapier is the answer that does not depend on our roadmap. The report fires as a trigger the moment the client submits it, and where it goes after that is your decision, not ours.
What every trigger carries
| Field on the trigger | Mappable in the Zap editor |
|---|---|
| Report title and the client's own words | Yes |
| Screenshot of the page as the client saw it | Yes, as a file URL |
| Exact page URL and where on it the client clicked | Yes |
| Browser, operating system and user agent | Yes |
| Viewport size and breakpoint | Yes |
| Priority and status of the report | Yes, and filterable |
| Which project the report belongs to | Yes, and per-Zap scoped |
Because priority is a real field rather than text, a Zap can branch on it — urgent reports page someone, cosmetic ones queue up for the next sprint.
Zaps agencies actually build
Linear or GitHub issues. New report in, issue out, screenshot URL in the body. The common setup for product teams that never adopted a project-management tool with a client-facing side.
A Google Sheet the client can see. One row per report, status column kept in sync. It is a low-tech answer and clients love it, because it is the one tool they already have open.
Escalation on urgent reports only. Filter the trigger on priority, then send a text message or page an on-call rota. Nobody has to watch a queue on launch night.
Your own endpoint. Zapier's webhook action posts the whole payload to a URL you control — the fastest route into an internal system that will never have a public integration.
When not to use Zapier
Worth saying plainly: if you are sending reports to ClickUp, Slack, Jira, Trello, Asana or Notion, use the native integration instead. It is fewer moving parts, it does not consume a task quota, and there is no Zap to quietly break when someone renames a field.
Zapier earns its place when the destination is something else, or when the routing needs a condition. Those are real needs, and they are exactly what a general-purpose automation layer is for.
Either way, your client is not involved. No Zapier account, no tapko.app account, no browser extension. They click where the problem is and type. Everything after that is wiring on your side.
Frequently asked questions
Which tapko.app triggers are available in Zapier?
Three: a new report submitted, a report whose status changed, and a new comment on a report. Each one is scoped to a project you choose, so a Zap watching one client never fires on another client's reports.
What data does the trigger carry?
The report title, the client's description, a URL to the screenshot, the page the report was made on, the click position, priority, status, and the browser, operating system, viewport size and breakpoint. Every field is individually mappable in the Zap editor, so you can send only what the destination app needs.
Do I need a paid Zapier plan?
A free Zapier plan runs single-step Zaps, which is enough to send reports into one destination app. Multi-step Zaps — filtering by priority, routing urgent reports differently, or enriching before sending — need a paid Zapier plan. That is Zapier's pricing, not ours; the tapko.app side is free on every plan.
Should I use Zapier or a native integration?
Use the native one where it exists. ClickUp, Slack, Jira, Trello, Asana and Notion connect directly, which means no Zap to maintain and no third-party task quota. Reach for Zapier when the destination is something we do not connect to natively, or when the workflow needs a condition, a filter, or a second step.
Does the Zapier integration cost extra?
No. Every tapko.app integration — Zapier, Slack, Jira, Trello, Asana, Notion and ClickUp — is included on every plan, including the free plan, which covers one project with no credit card and no expiry.