Skip to main content

Getting Started

Four steps to a working automation. About twenty minutes, most of it waiting for an installer.

StepWhat happens
1. Create a workspaceYour organisation's home, at yourcompany.robomotion.io
2. Install a robotThe software that does the work — Windows, macOS, Linux or Raspberry Pi
3. Connect the robotLink it to your workspace
4. Run your first flowWatch it work

Why the robot comes first​

The order matters, and it is the thing most people trip over.

Robomotion does not run your automations. Your robot does. The service stores flows and decides when they should run; the work happens on a machine you own, driving applications you own. So until a robot is connected there is nothing to run a flow on — which is why the Run button is greyed out on a fresh workspace, and why installing the robot is step 2 rather than an afterthought.

See Robot if you want the whole picture first.

Then pick how you want to build​

Once a robot is connected there are three ways to make a flow, and they suit different people.

Describe it to the AI Assistant. The Designer opens on a prompt box — "Build a flow that…" — and builds a first draft from a plain-language description. Fastest route from an idea to something running.

Start from a template. Over 250 ready-made flows in the template library, also reachable from the Designer's Start with an example. Importing one and changing it is how most people get their second automation done.

Build it node by node. Slower, and the only one that teaches you how flows actually work. The tutorial path takes this route deliberately — because understanding the message object is what lets you review what the Assistant produced rather than hoping it is right.

They are not exclusive. The common pattern is: let the Assistant draft it, then read and fix it — which requires the third skill.