Route support requests into a triage log
Every bug report lands in an Inbox table with severity and reporter, sorted so triage starts with the worst of them.
New submission on your support or bug-report form
Add a row to an Inbox table in Microsoft Excel with the issue summary, severity, requester email and arrival time
One-directional. A submission triggers the action — nothing is written back into your form.
Triage starts as a reading job: what came in, how bad is it, who picks it up. This flow puts each support or bug report into an Inbox table as it arrives, with the title, the severity and the reporter's email in separate columns.
Support leads use it when reports come from a public form and the team is small enough that a sorted sheet beats a ticketing tool. Sort by severity, work down, mark a Status column as you go — the Zap only appends, so nothing it writes disturbs the row you are editing.
Setting it up
- 1
Publish the bug report form with Severity as a fixed dropdown. Free-typed severities cannot be sorted into an order that means anything.
- 2
In your workbook, create an Inbox worksheet and format the header row as a table with columns for Received, Title, Severity, Rank, Reporter, Steps, Environment, URL, Status and Owner.
- 3
Put a Rank formula in the table — a nested IF that turns each severity label into 1, 2 or 3 — because Excel sorts text alphabetically and Critical would otherwise fall below Minor.
- 4
Leave Status and Owner unmapped. Triage writes into those two columns, and because submissions only ever flow into the workbook, an incoming row cannot overwrite them.
- 5
In Zapier, choose formformform's New Submission trigger, connect your account, select the bug report form and pull a real test report so every field appears in the mapper.
- 6
Add Microsoft Excel's Add Row to Table action, connect the Microsoft account, then select the workbook, the Inbox worksheet and the table.
- 7
Map Bug Title to Title, Severity to Severity, Email Address to Reporter and the trigger's submission time to Received, then send Steps to Reproduce into a wrapped column at the right.
- 8
Map Browser / Device and URL Where the Bug Occurs into Environment and URL, send a test report, sort by Rank to check the order behaves, then turn the Zap on.
What maps where
Using the Bug Report Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Microsoft Excel |
|---|---|
| Bug Title | Title column in the Inbox table |
| Severity | Severity column, converted to a sortable number by the Rank formula |
| Email Address | Reporter column, used when replying |
| Steps to Reproduce | Steps column at the right, Wrap Text on |
| Browser / Device | Environment column, filtered when a fault looks platform-specific |
| URL Where the Bug Occurs | URL column, clicked straight from the sheet |
Variations worth knowing
Add a second action after the Excel step, a Slack or Teams message that fires only when Severity is your top band. The row lands either way, so the log stays complete even for the ones somebody has already seen and picked up.
Map the trigger's submission ID into a Ticket column. Support can quote it when they reply, and when the reporter comes back a week later you can find the original row without searching through the description text.
If something isn't arriving
The field was added after the Zap was built, so Zapier is still mapping from an old sample. Pull a fresh test submission in the trigger step, map Severity again and re-test before switching back on.
Add Row to Table matches on header text, so renaming a header in the sheet orphans the mapping. Put the header back as it was, or reopen the action, remap the affected fields and re-test.
Frequently asked questions
Can we mark a bug fixed in Excel and have the reporter told?
Not through this connection. Rows only travel into the workbook, and a Status change in Excel goes nowhere on its own. Send the update from wherever you normally reply — the log records the decision, it does not deliver it.
How do we keep junk reports out of the table?
Put a Zapier Filter between the trigger and the Excel action so only submissions meeting your rule continue, a non-empty Steps to Reproduce for instance. Filtered submissions still sit in your formformform responses, so nothing is thrown away.
Is a spreadsheet enough for support triage?
For a small team sorting a handful of reports a day, a table with severity, status and owner columns is enough and everyone can already use it. Once you need assignment rules and response targets, point the same Zap at a ticketing app.
Related automations
- Aggregate survey and feedback responses
Each feedback response becomes a row with the score, the product and the comments, ready for averages and PivotTables.
- Build an order log for fulfilment
Every order appends a row to an Orders table, so quantities total themselves and the packing list is always current.
- Collect job applications in a hiring sheet
Applications land in a Candidates table you can filter by role and colour by stage as people move through the round.
- Log new leads to a tracking workbook
Each quote request becomes a row in a Leads table, with company, service type and budget already in their own columns.
- Track event RSVPs and registrations
Registrations append to an Attendees table, so the headcount totals itself and dietary needs are countable before the day.
- Add every inbound enquiry to your Notion leads database
Every business enquiry lands in your Notion Leads database as a page tagged New, with the company and inquiry type already filled in.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free