Visual workflow designer
- —Activity palette organised by category: web, desktop, files, data, mail, APIs
- —Visual branches, loops, parallel execution, and error handlers
- —One canvas view of the full automation from trigger to completion
Primo RPA Studio is the RPA development tool for building Primo automations. Citizen developers work visually with drag-and-drop, no scripting. Analysts add conditional logic and expressions. Engineers extend with custom code and libraries. All three roles work in the same project, publish to the same orchestrator, and run on the same robot. A built-in AI assistant works alongside each of them.

The assistant lives in a Studio panel next to Project and Activities. It reads a project the way a developer does — processes, variables, element properties, the activity catalog, code snippets, the Errors panel and the run log — and makes changes through the same operations Studio gives a developer. Describe a task in plain language: the assistant builds or updates the process, and you review the result.
Explain
Walks through an unfamiliar project: how processes connect, what each step does, where the data comes from.
Build and edit
Adds, moves and configures steps, edits variables and captures UI selectors. Creates new processes from a task description.
Check and troubleshoot
Runs the error check on the open process and reads the run log after a launch to find the step that failed.
Reuse what you have
Finds the right activity in the catalog, including NuGet packages, and follows your own code snippets as patterns.
You decide how much it can change
Your model, your perimeter
Connect any language model with an OpenAI-compatible API — a cloud service or a model on your own servers. With an on-premises model, projects and data stay inside your network. The assistant is part of Studio: no separate installation or license.
In Primo RPA Studio, no-code design, low-code automation logic, and full custom code are not separate tools — they are three views of the same project. A citizen developer starts a workflow visually. An analyst adds conditional logic. An engineer extends it with a custom activity. The same workflow file deploys to the same Primo RPA Robot, through the same Primo RPA Orchestrator, regardless of who authored each step.
No-code
Citizen developer
Low-code
Analyst
Full-code
Engineer
Moving from no-code to full-code doesn't rewrite the project — the same workflow file and all its steps remain unchanged.
A shared project file is necessary but not sufficient. What holds the three-mode model together is a set of runtime and platform decisions that Studio makes consistently — so that skills can mix without anyone inheriting work they did not author.
Differentiators
No rewrite between modes
Switch a step from visual to coded without changing the project file or breaking anything upstream.
Low-code automation on a shared runtime
Workflows built in no-code, low-code, or full-code all run on the same Primo RPA Robot — no conversion step.
Windows and Linux
Develop once, target both platforms. The same workflow deploys to either runtime without redevelopment.
Open SDK in C# and Python
Build custom activities that appear alongside pre-built ones in the activity palette.
Marketplace of pre-built components
Community and certified partner activities installable directly into Studio projects.
Native Git integration
Commit, branch, and diff from inside the IDE, without switching to an external client.