Quick answer: Create an Airtable table with columns named Status, Priority, Category, Platform, Version, Report #, Reporter and Bugnet, then connect it under Integrate > Integrations > Airtable with a personal access token. Each new crash or in-game report adds a record with the title in the primary field and matching columns filled, and Status follows the bug. Included on every Bugnet plan.

Airtable is a favourite with game producers and QA leads because it is a spreadsheet that behaves like a database: filtered views, grouped reports, forms and automations. As a bug tracker it has one weakness, the same as every spreadsheet: somebody has to type the bugs in. This guide removes that step.

A bug tracker table for games

Bugnet fills columns whose names match its fields, ignoring case, and skips columns it does not recognise or that are computed, so you can keep your own columns alongside.

ColumnSuggested typeWhat Bugnet writesAlso matches
Name (primary field)Single line textThe bug's titleYour primary field, whatever its name
StatusSingle selectOpen, In progress, Resolved, Closed, Won't fixState, Stage
PrioritySingle selectCritical, High, Medium, LowSeverity
CategorySingle selectCrash, Gameplay, Visual and so onType, Kind
PlatformSingle select or textWindows, Android, Web…Platforms
VersionTextThe game version of the reportGame version, Build
Report #NumberBugnet's report numberReport number, Bug #
ReporterTextThe reporter, or “Player (anonymous)”Reported by, Player
BugnetURLA link to the full reportLink, URL
DescriptionLong textThe report textDetails, Notes, Summary

New select options are added as needed, so you do not have to pre-create every platform or version.

Connecting it

1. Capture bugs in the game

Create a free Bugnet project and add the SDK for your engine (Unity, Unreal, Godot, GameMaker, Construct 3, Pygame or web). Crashes are captured automatically with logs, a screenshot and hardware details; players report the rest through an in-game widget.

2. Create an Airtable token

At airtable.com/create/tokens, create a personal access token with the data.records:read, data.records:write and schema.bases:read scopes, and give it access to your base.

3. Pick the table

In Bugnet, open Integrate > Integrations > Airtable, paste the token, choose Load tables, pick the bug table and choose whether to add a record for every new bug (or only some, with the priority filter) and whether to update Status as bugs change. Choose Connect.

Views that make it useful

How the team works with it

Repeat reports stack onto one Bugnet bug, so Airtable gets one record per bug, not per occurrence; the occurrence count and full context live behind the Bugnet link. Status flows from Bugnet to Airtable, so change status in Bugnet: the record updates, the player who reported it hears back if they left an email, and the fix goes into your next auto-drafted changelog.

The same column matching powers the Notion and monday.com integrations. Details are in the integration docs.

Frequently asked questions

Can I use Airtable as a game bug tracker?

Yes. A table with Status, Priority, Category, Platform and Version columns works well, and Bugnet can add a record for every new crash or player report automatically.

Which Airtable token scopes does Bugnet need?

A personal access token with data.records:read, data.records:write and schema.bases:read, with access to the base that holds your bug table.

Do I need to create select options in advance?

No. Bugnet adds new select options as needed.

Does Airtable get a record for every crash occurrence?

No. Repeat reports stack onto one Bugnet bug with an occurrence count, so Airtable gets one record per bug.

Is the Airtable integration free?

Yes. It is included on every Bugnet plan, including the free plan.

A spreadsheet is a great bug tracker right up until someone has to fill it in. Let the game do it.