All templates

Automated Bravo Studio Build Export Handoff

Every few hours, WebRun opens Bravo Studio, checks for app builds that finished exporting, saves the build package to a shared Google Drive folder, and posts a Slack message to the QA team naming the build and linking straight to it for testing.

Deploy this workflow Browse all templates

Runs on WebRun · Strict Lockdown policy

Every 4 hours WebRunorchestrates each step

Bravo Studio check for finished exports

Google Drive save the build package

Slack notify the QA team

In short

How do I automatically hand off Bravo Studio app builds to QA?

WebRun checks Bravo Studio every few hours for app builds that finished exporting, saves the build package to a shared Google Drive folder, and posts a Slack message to the QA team naming the version and linking straight to it. A finished export turns into a QA-ready handoff without a developer manually downloading and sharing the file.

Finished builds reach QA within hours, not whenever someone remembers
Every build package is saved with a clear version and platform
Failed exports never get handed off as testable by mistake

Built for Mobile app teams · no-code developers · QA testers · small product teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

WebRun signs in and gets to work

Opens bravostudio.app in a real browser with your saved login - no setup, no API keys.
1
Bravo Studio - check for finished exports

bravostudio.app

WebRun checks for finished exports in Bravo Studio.
- Open the project and check the export queue
- List any build that finished since the last check
- Note the version and platform for each
Done when Every newly finished export is listed.
2
Google Drive - save the build package

drive.google.com

WebRun saves the build package to Google Drive.
- Save each build package to the shared QA folder
- Name the file with the app, version, and platform
- Keep prior builds for reference
Done when Every finished build is saved to Drive.
3
Slack - notify the QA team

slack.com

WebRun notifies the QA team in Slack.
- Post a message to the QA channel naming the new build
- Link to the build package in Drive
- Tag whoever is testing this cycle
Done when The QA team has a Slack message linking to the new build.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run

bravostudio.app

ScheduleRuns automatically on this cadence

Every 4 hours

DeliveryHow each run's result reaches you

Build ready alert · Slack

OutputWhat each run produces - A saved build package in Google Drive for every finished export, with a Slack notification to QA.

Text

Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.

Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST

Typed input ALLOW

Shell command BLOCK

File uploads BLOCK

Runs in a contained environment More on policies

Good to know

Questions, answered

Does it publish the app to the App Store or Play Store?

No. WebRun only saves the build package and notifies QA. Publishing to a store stays a manual step your team takes.

What if an export fails?

It's skipped from the handoff and noted, so a broken build never gets sent to QA as ready for testing.

Can it handle more than one app project?

Yes. Point it at any project in Bravo Studio and it picks up finished exports from that one.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.

Deploy this workflow Talk to us