Create an Airtable record for every new BugBug test

Every time a BugBug test run finishes, this workflow creates a new record in the Airtable base and table you choose, so you build a running log of test runs without copying results by hand.

BugBug

Airtable

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 385 sites Free to import

The Create an Airtable record for every new BugBug test workflow on the FlowMattic canvas, with 2 steps across BugBug, Airtable — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

BugBug runs your browser tests, but looking back over weeks of runs means opening each one in the BugBug app. An Airtable table gives you one place to sort, group and comment on runs. This workflow adds a record there each time a test run ends.

The BugBug trigger is Test Finished. BugBug has no trigger for a newly created test, so the workflow fires when a test run finishes, not when you add a test to your project. Every finished run starts it, re-runs of the same test included, so one test that you run five times becomes five records.

The run details BugBug sends are passed to Airtable, where the Create Record step adds a new row to the table you pick. You decide which Airtable fields receive which values. The template ships with no mapping, so finish one test run after import and use the captured data to set up the fields.

Each run of the workflow appears in Task History, where you can see the data BugBug sent and what Airtable returned.

A history of test runs for the QA lead

Each finished BugBug test adds a row, so the QA lead can group the Airtable table by test and see how often each one ran over the sprint.

Release checklist evidence

Before a release, the team runs the key BugBug tests. The Airtable records give a dated list of those runs to link from the release checklist.

Spotting tests that need attention

Map the run details into Airtable fields, then build an Airtable view that groups records by test, so tests that run often stand out at a glance.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
BugBug Test Finished
Fires each time a test run finishes in your BugBug account, including repeat runs of the same test. The run details BugBug sends become available to map in the Airtable step.
Step 2Action
Airtable Create Record
Adds one Airtable record per finished BugBug test run, in the base and table you pick. Map the BugBug run details to your table's fields after import, and connect your Airtable account.

What you need

FlowMatticCore
BugBug AccountAccount
Airtable AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Finish one BugBug test run after import so FlowMattic captures the data it sends. Then map those values to your Airtable fields and check the record in Task History.
If you only want some runs logged, add a Filter between the two steps and set it on a value from the BugBug data, after a test run shows you what that data holds.
Want a ping as well as a record? Add a Slack or Discord step after Airtable so the team sees each finished run where they already talk.

Questions about this workflow

Does creating a new test in BugBug start this workflow?

No. BugBug's triggers in FlowMattic are for runs starting and finishing. This template uses Test Finished, so a record is created only when a test run ends.

Will re-running the same BugBug test add another Airtable record?

Yes. Every finished run starts the workflow, so each re-run of a test creates its own record. Airtable does not merge them.

Which BugBug details can I store in Airtable?

Whatever BugBug includes with the finished run. The template has no fields mapped, so finish one test run after import and look at the captured data before you set up the Airtable fields.

Do whole suite runs trigger this workflow too?

This template listens for Test Finished only. BugBug also offers Suite Finished and Schedule Finished triggers in FlowMattic, so swap the trigger if those are the runs you want to log.