Percy on BrowserStack tells you when a visual build is created, finished, approved or sent back with changes requested. FlowMattic writes each of those moments to Google Sheets, giving QA leads and release managers one row per build with its branch and review state, a log they can filter by release without opening every build.
12 triggers 19 actions 6 example workflows 2 ready-made templates Unlimited runs
When this happens in BrowserStack6 triggers
Do this in Google Sheets19 actions
1. TriggerBuild Finished2. ActionAdd New RowWhen BrowserStack fires Build Finished, FlowMattic runs Add New Row in Google Sheets with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateWhen Percy finishes processing a build, its ID, branch, commit and snapshot details are written as a row, so the team has a history of visual test runs per branch.
Build FinishedAdd New Row
View the template Find the build's row by its ID and write the approval and date into it. Release managers can see at a glance which builds were signed off before a deploy.
Build ApprovedLookup Row DataUpdate Row
Each build sent back by a reviewer goes into a fix list with its branch and link, and an email to the front-end team points them to the new row.
Build Changed RequestedAdd New RowEmail (SMTP)
Starting the log at Build Created gives every build a row from the beginning, so a build that never finishes or never gets reviewed stands out in the sheet.
Build CreatedAdd New Row
Feature branches create a lot of builds. A Filter keeps the log to main and release branches, so the sheet answers one question: was this release visually reviewed.
Build FinishedFilterAdd New Row
If a reviewer undoes a changes-requested decision, Build Unreviewed finds the row and clears the old status, so the fix list does not show work that is no longer needed.
Build UnreviewedLookup Row DataUpdate Row
At the end, every Percy build that finishes processing adds a row to your build log.
Create a sheet with Build ID, Project, Branch, Commit, State and Finished at columns.
Create a workflow with BrowserStack and Build Finished, then add the webhook details the trigger shows to your Percy project's webhook settings.
Push a commit or rerun a build so FlowMattic receives a finished build and its fields.
Connect Google Sheets, add Add New Row, map the build ID, branch and state to their columns, test and switch the workflow on.
1. Trigger in BrowserStack
Build Finished
2. Action in Google Sheets
Add New Row
Fields mapped from the earlier steps (a typical setup)
| From BrowserStack | To Google Sheets |
|---|---|
| Build ID | Build ID |
| Project name | Project |
| Branch | Branch |
| Commit SHA | Commit |
| Build state | State |
| Finished at | Finished at |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
BrowserStack and Google Sheets connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
The sheet keeps every build and its review outcome in one place you can sort, filter and attach to a release checklist.
Build and commit details go from BrowserStack through your own WordPress site to Google, not through another automation account.
Runs are unlimited, so a pipeline that creates dozens of builds a day costs nothing extra to log.
Percy visual builds. The triggers cover a build being created, finished, approved, sent back with changes requested or returned to unreviewed, plus the Ping event for webhook configuration.
Yes. Add the row at Build Created or Build Finished, then use Lookup Row Data and Update Row in workflows for Build Approved and Build Changed Requested to fill in the outcome.
Yes. Use a Router on the project name and point each path's Add New Row at a different sheet in the same spreadsheet.
Each FlowMattic workflow has its own trigger, so set up the webhook that each workflow's trigger shows. A project can send to several workflows, one for finished builds and one for approvals.
Did not find your answer? You can browse the help center or ask us directly.
Google Sheets and Slack149 shared templates
Google Sheets and AI Agents26 shared templates
Google Sheets and Fluent Forms23 shared templates
Google Sheets and WooCommerce20 shared templates
Google Sheets and FluentCRM19 shared templates
Google Sheets and WPForms12 shared templates
Google Sheets and ActiveCampaign11 shared templates
Google Sheets and Gmail11 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. BrowserStack integration 1.0.0, Google Sheets integration 2.2.4.
