---
title: The Flow Editor
description: "The Flow Editor in Core: build processes by connecting blocks, watch the real data run through them live, roll back any version, with validation before go-live."
url: "https://rual.nl/en/visual-editor"
locale: en
alternate: "https://rual.nl/visual-editor"
updated: 2026-08-03
source: "https://rual.nl"
---

# In the Flow Editor you build by connecting blocks.

The Flow Editor is the canvas of Core. You drag blocks onto the screen, connect them, and see straight away what runs through them.

[Book a demo](https://rual.nl/en/demo)

[See Studio](https://rual.nl/en/studio)

![Screen recording of the Flow Editor: blocks are dragged onto the canvas and connected to one another.](https://rual.nl/site-assets/_opt/blueprint-960.webp)

## Every flow is made of blocks

A block does one thing and hands the result to the next one. There is not much more to it.

- **A trigger starts it** — An incoming order, a scan on the floor, a file in a folder or simply the clock. The starting block decides when the flow runs.

- **Blocks do the work** — Read, calculate, decide, store, send. For logic and data, and just as much for Exact, Mollie, a ZPL printer or a DOBOT robot.

- **Connections carry the data** — The line between two blocks is the route your data takes. You split, merge and loop back by dragging a line.

**Over 2,800 blocks are ready to use.** From date calculations to a connection with your accounting. If one is missing, we build it and maintain it too.

[See the block library in Studio](https://rual.nl/en/studio)

## See what happens, while it happens.

The editor does not sit beside your process, it sits inside it. Click a block and you see the real values passing through it at that moment: which order numbers, which stock lines, what the integration answered.

When something stalls you see exactly which block, and with what data. No log lines to add, no redeploy, no reconstructing it afterwards.

- Live values per block, during execution
- Execution time per block, down to the nanosecond
- Trying things out in a test environment, separate from production

**studio.rual.nl · Flow Editor**

One execution of an order flow, the way the editor shows it.

- `webshop.order` — trigger · new order

- `stock.check` — reserves 3 order lines

- `wms.picklist` — to station 4 in the warehouse

- `exact.invoice` — posts straight into Exact Online

- `mail.tracktrace` — sends the customer a track & trace

**execution · order #29,107**

- `00:00.000` webshop.order, order #29,107 received

- `+180 ns` stock.check, 3 order lines reserved

- `+1.2 µs` wms.picklist, station 4 instructed

- `+2.1 µs` exact.invoice, posted in Exact Online

- `+0.4 ms` mail.tracktrace, customer notified

- `done` flow completed, 6 blocks in 0.4 ms

## Every version stays.

A flow is living work, so the editor records what changes and turns rolling back into a button instead of a project.

- **History per blueprint** — Who changed which block, and when, is on record. You open an older version and compare it with what is running now.

- **Roll back in one step** — If a change turns out badly you put the previous version back. No rebuild, and no data disappears.

- **Validation before go-live** — The editor checks your blueprint for broken connections and missing fields before anything moves towards production.

- **Controlled rollout** — Going straight to live is allowed, but not required. You stage changes, have them reviewed and release them when it suits you.

### The Flow Editor is one window in Studio.

Studio is everything around it: the block library, comments on blocks, deploy management and usage statistics per environment.

[See Studio](https://rual.nl/en/studio)

## Want to build a flow in the editor yourself?

In a demo you take the mouse and we put down a first flow of your own process together.

[Book a demo](https://rual.nl/en/demo)

[See the platform](https://rual.nl/en/platform)