Installs in ~2 min· 2 assets · 7 steps

Route every bug to the right engineer, already triaged

A bug reaches the right engineer already triaged, before anyone in support has to read a stack trace.

Customers report bugs through a form. AI reads the description and the attachments, categorizes the issue, estimates its severity, links it to anything similar already reported, and writes a summary for engineering. It's assigned to the right team automatically, with that summary attached.

Free · no credit card · you connect your own apps

The blueprint
Trigger
Report a Bug is submitted
Every run starts from one submission.
Transform
Read Screenshot
AI reads the input and returns a structured result.
Transform
Find Similar Bugs
Transform
AI Triage
AI reads the input and returns a structured result.
Action
Notify Team
What gets built

2 things appear in your workspace.

Installing provisions each one, wired together and ready to run.

FormReport a Bug

form capturing the description, severity, steps to reproduce, browser and device information, and optional screenshots or log files. Publishing it auto-creates the Bug Reports response sheet, which is the single system of record and dashboard.

WorkflowTriage & Route Bug

Fires on submission. Reads the report and its attachments, categorizes, estimates severity, links similar issues, writes the engineering summary, assigns the team, and notifies them.

What you connect

The apps this recipe needs.

You connect your own accounts. Swap any app that offers an alternative at install.

Notification
Slack *

Posts each triaged bug (engineering summary, category, severity, and the assigned team) to a single shared engineering channel with a link back to the Bug Reports sheet. Swap for Telegram, Discord, or Google Chat.

How it works

Step by step, once it is running.

  1. 01
    Customers Report the Bug

    A form captures the bug description, the severity they'd assign it, the steps to reproduce, their browser and device information, and optional attachments such as screenshots or log files. Everything engineering needs, asked for once, upfront.

  2. 02
    Every Report Is Logged

    Each submission is stored automatically in TinyTables with an initial status of New.

  3. 03
    AI Reads the Report and the Attachments

    It analyzes the bug description along with any attached screenshots or text-based files to categorize the issue (UI, Performance, Login, Payments, and so on), estimate its severity, identify similar previously reported issues, and generate a concise summary for the engineering team.

  4. 04
    Duplicates Are Linked Together

    Where similar bug reports already exist, AI links them, so a recurring problem surfaces as one issue with a pattern behind it, instead of five disconnected tickets nobody connects.

  5. 05
    It's Routed to the Right Team Automatically

    Based on the category and severity, the report is assigned to the appropriate engineering team, who receive an email or Slack notification containing the AI summary and a link to the record in TinyTables.

  6. 06
    Engineers Work It to Resolution

    They review the bug, update its status in TinyTables (In Progress, Resolved, Closed) and collaborate on the record itself rather than in a side thread.

  7. 07
    One Dashboard Shows Everything Open

    TinyTables provides a centralized dashboard where engineering and product teams track open bugs, monitor severity, identify recurring issues, and measure resolution progress.

What you walk away with
FAQ

Questions about Bug Report Intake & Engineering Routing.

What do I need to connect?
Slack, and that is the only integration. Every triaged bug is posted to one engineering channel with its summary, category, severity and assigned team. You can swap Slack for Telegram, Discord or Google Chat at install.
Where do the bug reports themselves live?
Publishing the Report a Bug form auto-creates its Bug Reports response sheet, and that sheet is the single system of record and dashboard. You paste its view link at install so each Slack post can deep-link straight to the full report.
How does it decide which team owns a bug?
It routes to a team you have named. AI reads the report, categorizes it and estimates severity, then assigns it to the owning team from your list. Routing can only assign to teams you configured, so it never invents an owner.
Does it handle duplicate reports?
Similar issues are linked together rather than landing as unrelated rows, so a bug reported by five customers reads as one problem with five reports instead of five separate tickets competing for attention.
What does the reporter have to fill in?
The form captures the description, severity, steps to reproduce, browser and device information, and an optional screenshot or log file. That structure is what lets AI triage accurately instead of guessing from a one-line complaint.
More recipes

Install it, then make it yours.

Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.