Skip to main content

Tutorials

These tutorials are a path, not a menu. Each one is short — ten to fifteen minutes — and each teaches exactly one idea, building on the one before it. Work through them in order and by the end you will understand not just which buttons to press, but why RPA flows are shaped the way they are.

Tutorials 4 and 5 are built on real templates from the library, so you can import the finished flow and compare it against your own. The library is in the Designer under Start with an example, or at robomotion.io/templates.

Before you start​

You need a workspace and a connected robot. If you do not have those yet:

  1. Create a workspace
  2. Install a robot
  3. Connect the robot

The path​

#TutorialThe idea it teaches
1Your first flowWhat a flow, a node and a robot actually are
2Passing data between nodesThe message object — the one concept everything else rests on
3Making decisionsBranching, so a flow can react to what it finds
4Repeating workLoops, and why RPA pays off at volume
5Handling failureTry/Catch — the difference between a demo and production
6Working with Excel dataReading a spreadsheet into a flow
7Automating a browserSelectors, and the Inspect tool

Worked examples​

The path teaches one idea per tutorial. These put several together to do a real job, and each one is a complete flow you build from an empty canvas.

ExampleWhat you end up with
Stock prices into ExcelReads symbols from a spreadsheet, looks up each price in a browser, writes it back
Convert currency in a browserAsks for an amount, scrapes the conversion off a search page, shows the result
Write a CSV fileBuilds a table in code and writes it out
Post a message to DiscordA bot that posts to a channel, with its token kept in a vault

What is RPA, in one paragraph​

Robotic Process Automation is software that operates other software the way a person does. Instead of asking a vendor for an API, a robot opens the application, clicks the button, reads the screen and types the value — so it can automate systems that were never designed to be automated. Robomotion adds two things to that: a visual flow so the sequence is something you can see and reason about, and AI nodes so steps that need judgement rather than rules can be handled too.

The seven tutorials in the path are, in order, the smallest set of ideas you need to build that yourself. The worked examples are what those ideas look like once they are doing something useful.