From request to checked flow
Roubot is a desktop app. You describe a task in the chat, it turns it into a step-by-step flow, and you can see and change that flow in a visual editor before running it.
Six steps
Say it in your own words
You ask for the automation in the chat in your own words ("I want that, when a claim arrives by email, you register it on the insurer's website") and Roubot proposes the flow on a card that you review before saving it.
Review the flow
Roubot is a desktop app. You describe a task in the chat, it turns it into a step-by-step flow, and you can see and change that flow in a visual editor before running it.
A flow prepared by the chat is born switched off: it does not run on its own until you switch it on.
Rehearse it with no side effects
A flow can be rehearsed with no side effects: reads happen for real and the steps that would leave the machine are simulated, recording what they would have done.
Switch it on
A flow starts by hand, at a set time, or when an email arrives (it then checks the mailbox every minute while it is switched on).
Every step, checked
The outcome is decided by a check, not by what the action reports: a sent email is looked up in Sent; a file or a sheet is opened again. If the check says it did not happen, the step fails.
A check has three possible answers: it happened, it did not happen, or there is no way to tell. "No way to tell" never counts as done.
See what happened today
The "What happened today" screen shows, in plain words, what is waiting for a person and what failed; below that, each run of the day with its steps, and the scorecard of each automation.
What it works with
The steps work with what an office already uses: email, folders and files, Word and PDF, Excel and CSV, web pages, desktop programs and databases.
Roubot's catalogue has 136 action types in 9 families. 114 already have their action built; the rest are in the catalogue waiting for theirs. The examples in the table are all from the ones that have it.
Every Roubot action has its type in a shared catalogue —read a document, append rows to a sheet, send an email…— and each type states whether it leaves the machine, whether it can be undone and how it is checked.
| Family and examples | Types | With an action today |
|---|---|---|
Files and folders See what is in a folder · Move or rename a file · Find files by name or content | 12 | 10 |
Documents: Word, PDF and similar Read a document · Fill in a document template · Change an existing document, keeping its format | 11 | 10 |
Spreadsheets and tabular data Read a sheet or CSV as a table · Append rows to a table · Go through a table row by row | 14 | 8 |
Email, messages and calendar Read emails · Leave an email in drafts, without sending it · Save an email's attachments to disk | 16 | 10 |
Web and program interfaces Get the text or links of a page · Check whether a page has changed since last time · Type into a field of a page or a program | 21 | 19 |
Databases and APIs Query a database · Read data from an application through its API · Search what is recorded in Roubot | 17 | 17 |
Transform, extract and compare data Extract data · Look at an image: describe it or read what it says · Do a calculation with some data | 11 | 8 |
Execution: conditions, waits, approval and retries Ask a person for approval · Decide which branch to follow · Check from outside whether an act happened | 21 | 19 |
System and processes Launch a program or a command, and talk to it · See how Roubot or the machine is doing · Make a backup | 13 | 13 |
By which route
For each job it uses the most solid route available: the official API, the application's own API, the accessibility tree, the web page or the files. Looking at the screen and moving the mouse is the last resort.
The accessibility-tree and vision routes work on macOS today.
- Official APIsolid
- The application's private APIsolid
- Accessibility treesolid
- Browser DOMsolid
- Files and macrosmedium
- Vision and simulated typingfragile
Use cases by area
Roubot is tested with requests written the way a person writes them. These are the ones in the test bench, by area.
Insurance
- When an email reaches the claims inbox, take out the attachments, read the report, validate the policy in the insurer's system and register the claim.
- Look up a list of policies, one by one, in the insurer's system and note in a CSV whether each one is in force.
- Every hour, look up a policy in the system and leave a draft email saying whether it is in force and until when.
Administration and finance
- When an invoice arrives by email, save the PDF in a folder and note the date, invoice number and amount in an Excel file.
- From each PDF receipt in a folder, extract the date, the shop and the total, and put it all in an Excel file.
Management and office
- Every morning at 8, summarise the unread emails and save the summary in a Word document.
- On Mondays at 9, check which files are in a folder and write a Word report with the list and how many there are.
- Translate the text of a file into English and save it in another file.
The demo, from start to finish
Roubot's demo: an email arrives with three photographed documents and out comes a claim file set up in the management system, archived, with an acknowledgement drafted and waiting for approval. The flow stops before writing anything in the system until a person approves.
- Arrives
Checks whether an unread claim has arrived.
- Saves
Saves the three attached photos to the claim file.
- Looks
Looks at the photos of the report and the quote and fills in the record.
- Looks up
Looks up the policy in the system before writing anything.
- Waits for a person
Shows what it extracted, highlights in amber what does not match and waits for a person.
- Fills in
Fills in the ten fields and saves the claim as pending.
- Files and records
Files the documents, writes the acknowledgement without sending it and leaves a Word record.
Where it runs
- Today Roubot installs on macOS, on Apple Silicon or Intel. The Windows and Linux builds are set up but not yet properly tested.Today
- The app is available in Spanish and English.Today
- No: today Roubot needs the internet for the chat, for building flows from a request and for looking at images, because it uses cloud AI models. What a flow does with your files happens on your computer.Today
See it working on your own work
Tell us about a task that repeats in your organisation and we will show you how it would look as a flow, with its log.
hola@roubot.ai