Browse docs
Page sections
Product docs
Build Studio: Step-By-Step Guide
A plain-language walkthrough of installing Build Studio, recording an automation, reviewing it, and publishing it to your team, plus troubleshooting and FAQ.
Summary
- Recording, compiling, reviewing, and publishing an automation is one continuous flow inside a single group page.
- Apps are connected once per group, not once per automation, and every recording starts already signed in.
- Publishing prepares a release; a separate, deliberate step in Conxa Cloud is what actually sends it to your team.
What this guide covers
This is a practical, step-by-step companion to the Build Studio overview above. It walks through installing the app, recording a task, fixing anything that looks off, and getting it in front of your team, plus what to do when something goes wrong.
It is written for anyone using Build Studio day to day, not just engineers. Technical setup details are called out separately where they matter.
Installing Build Studio
- Sign up at the Conxa dashboard and download the Build Studio installer for Windows.
- Run the installer. The first launch downloads a few one-time dependencies, including a bundled browser engine, which can take a few minutes on a slow connection.
- Sign in when prompted. This opens your normal web browser to a secure sign-in page; Build Studio picks up the result automatically once you finish there.
On a locked-down network
If downloads stall, the setup screen shows the exact web addresses it is trying to reach. Give those to your IT team to allow through the firewall or proxy.
Connecting the apps you'll automate
Automations are organized into groups, like folders for a business area such as Sales or Finance. Before recording the first automation in a group, connect the apps (websites) it uses, once per group rather than once per automation.
- Open a group and find the Applications panel.
- Add an app: give it a name, its login page, and the page you land on once signed in successfully.
- Click Connect next to the app. A browser window opens to its login page, sign in normally.
- Once you land on the page you specified as signed in, the window closes on its own and the app shows as connected.
Saved logins stay local
Every automation recorded in that group starts already signed in to every connected app. Saved sessions are stored locally and encrypted on your machine, and are never included in anything you publish or in any installer you build.
Recording an automation
- In a group, create a new automation with a name and a starting web address.
- Start the recording. A browser window opens, already signed in to the group's connected apps.
- Do the task exactly as you normally would: click, type, select menus, fill forms, switch tabs, upload files.
- Close the recording window and save it once you are done.
- Multiple tabs: opening a new tab mid-task, or switching between tabs, is captured in order and replayed the same way later.
- File uploads: Build Studio remembers the file's name, not its location on your computer, so anyone running the automation later supplies their own copy.
- Optional pop-ups: a cookie banner or confirm dialog you interacted with is flagged during review as a candidate to treat as optional, rather than guessed at automatically.
Compiling
Compiling turns a saved recording into a structured automation, typically in under a minute to a few minutes depending on the length of the recording, with a progress view while it works.
A first compile uses one of your compile credits. Re-compiling an automation you have already compiled draws from a separate, smaller AI Usage Credits pool instead. Both meters are visible at the top of the screen.
Reviewing in Human Edit
After compiling, open the automation for review. This is where every step gets checked and fixed before it goes live.
- Edit what a step does, or which input field it fills.
- Reorder, insert, or delete steps.
- Turn a value typed during recording into a variable the AI assistant asks for each time, instead of a fixed value.
- Re-target a step pointing at the wrong element: draw a box around the correct one, review the suggested options, and confirm what should be checked afterward to know it worked.
A banner at the top honestly reports whether the whole automation looks solid or has steps that need a second look, with links straight to any flagged step. Approving the automation packages it automatically if every automation in the group is compiled and approved, with no separate build step to remember.
Testing
Before publishing, run the automation once against the local Conxa runtime to watch it complete, or see exactly where it fails, before your team relies on it.
Publishing and releasing
- Open Publish Skill Package and pick the automation being released.
- Review the plain-language summary of what is changing compared to the last published version.
- Enter a version number and short release notes, then publish.
Publishing is not the same as releasing
Publishing prepares an immutable, versioned release. Making it actually go live to your team is a separate, deliberate action taken by an admin in the Conxa Cloud dashboard, so a publish never quietly reaches everyone without a second confirmation. Once released, everyone's installed runtime picks up the update automatically, typically within a minute, with nothing to reinstall.
Building an installer
Most routine updates never need this: publishing is enough for anyone who already has Conxa installed. Building an installer is only needed to distribute Conxa to a machine for the first time, and requires that at least one automation has already been published.
Troubleshooting
| Problem | What to do |
|---|---|
| Setup or a download got stuck. | Re-launch Build Studio; setup resumes and skips anything already installed. On a corporate network, allow the addresses shown on the setup screen through your firewall. |
| Signed in, but the app did not notice. | The sign-in window can take a few minutes to time out. Close and reopen Build Studio, then try Sign In again. |
| An app shows as expired or not connected, but you are logged in on the website itself. | Build Studio keeps its own saved login separate from your regular browser. Reconnect (or Connect) that app's row and sign in inside the window it opens. |
| Recording will not start. | Recording is blocked until every app the automation needs is connected in that group. Check the Applications panel for anything still needing sign-in. |
| A step keeps failing when testing. | Open the step's reliability details in review; it usually shows the recorded element could not be found the same way anymore. Re-target it by drawing a box around the correct element, then re-test. |
| Out of compile credits or AI Usage Credits. | Check the usage meters at the top of the screen for what is left and when they reset. Editing steps directly does not use quota; only AI-assisted actions like re-generating a selector do. |
| Publish failed. | Build Studio states plainly what did not upload and why, and nothing partial is marked as published. Fix the issue shown and publish again; it is safe to retry. |
| Installer build says a skill pack has not been published yet. | Publish an automation first; the installer packages an already-published release rather than creating one. |
Does Build Studio need special access to the websites I automate?
No. It works the same way a person does, by opening a real browser and interacting with the page. There is nothing to configure on the target website itself.
Where do the recorded logins get stored?
Locally on your computer, encrypted. They are never uploaded, published, or included in anything distributed to customers or teammates.
What happens if the website changes after I publish an automation?
Small changes, like a moved button or a renamed label, are adapted to automatically. A bigger redesign may need a human to look at it again; that is flagged the same way a failed run is, rather than failing silently and repeatedly.
I released a bad version, can I undo it?
Yes. From that automation's release history in the Conxa Cloud dashboard, an admin can roll back to any previously released version with no rebuild needed, and it only affects that one automation.
Related docs
Build Studio
How builders record, edit, compile, test, and package workflows before publishing them to Conxa Cloud.
Platform Overview
How Conxa turns recorded software workflows into local MCP skills that AI tools can execute reliably.
Runtime And MCP Execution
How the installed runtime exposes local browser workflow automation to Claude Desktop or another MCP client and executes skills locally.
Support
How to contact CONXA for product help, billing questions, security reports, privacy requests, and enterprise procurement.
On this page