INTEGRATION
tapko.app + Trello
Your client clicks on the broken thing and types a sentence. A card appears in your list with the screenshot as its cover, so you can triage the whole week's feedback from the board view without opening a single card.
The gap this closes
Trello works because you can see the whole job at a glance. That is also what breaks when client feedback arrives badly — a card called “fix the thing on mobile” with no screenshot and no URL tells you nothing from the board view, so somebody has to open it, read it, and then go and ask what the client meant.
The usual fix is discipline: a team member reads every incoming email or WhatsApp message and writes a properly formed card. That works right up until the week before launch, when the person doing it is also the person building.
The Trello integration makes the card properly formed at the moment the client makes the report. Screenshot on the front, context inside, in the list you chose.
What lands on the Trello card
| Captured on every report | Where you get it |
|---|---|
| Report title and the client's own words | Card name and description |
| Screenshot of the page as the client saw it | Attached, and shown as the cover |
| Console logs, when the widget captured them | Attached to the card |
| Exact page URL and where on it the client clicked | One click from the card |
| Browser, operating system and user agent | One click from the card |
| Viewport size and breakpoint | One click from the card |
| Priority and status of the report | One click from the card |
The screenshot on the cover is the part that changes how triage feels. You can sort a Monday morning's worth of reports into real and cosmetic without opening anything.
Setting it up
1. Authorise Trello. Open Plugins in your tapko.app account and click Connect on Trello. You approve access on the Trello screen and are returned immediately. There is no API key and token pair to generate or keep safe.
2. Choose the board and list. In the project you want to sync, pick the workspace, then the board, then the list new cards should arrive in. Each tapko.app project points at its own board, so one client's reports never land on another client's board.
3. Share the project link. Send your client the link. From their next report onwards, cards appear in the list you chose.
Disconnecting is the same route in reverse — Plugins, Disconnect. The stored authorisation is deleted and syncing stops. Cards already on your boards stay exactly where they are, attachments included.
Your client never sees the board
Sharing a Trello board with a client is the obvious move and it almost always backfires. They see cards they were never meant to see, they comment on work in progress, and they start treating the board as a wishlist. Then you spend a call explaining what “blocked” means.
tapko.app keeps the board yours. The client gets a link to their own site with a widget on it — no Trello account, no board invite, no tapko.app account, no extension. They click where the problem is and type. The card appears on your side, in your list, in your workflow.
That separation is what makes the process last past the first project. Your board stays a working tool rather than a client-facing artefact you have to keep tidy.
Frequently asked questions
Does my client need a Trello account?
No. Your client never touches Trello. They click on the page where they see the problem and type a comment — no Trello account, no board invite, no tapko.app account, no browser extension. The card appears on your board, not theirs.
What ends up on the Trello card?
The card name is the report title and the description is the client's own words, with the screenshot attached — so it shows as the card cover and you can triage straight from the board view. Console logs are attached too when the widget captured them. A link on the card opens the full tapko.app record with the page URL, the click position, and the browser, operating system, viewport size and breakpoint.
Which list do new cards go into?
Whichever list you choose per project. Most teams point it at a dedicated Reported or Inbox list at the left of the board, so client feedback arrives in one place and gets dragged into the real workflow during triage rather than landing mid-sprint.
Can different projects sync to different Trello boards?
Yes. The Trello connection is made once for your account, and the destination board and list are chosen per tapko.app project — so each client's feedback lands on that client's own board.
Does the Trello integration cost extra?
No. Every tapko.app integration — Trello, Slack, Jira, ClickUp, Asana, Notion and Zapier — is included on every plan, including the free plan, which covers one project with no credit card and no expiry.