---
url: /visual-process-editor.md
description: >-
  Documentation for MODLR, the corporate performance management and planning
  cloud.
---

# Visual Processes

Visual Processes let you define and orchestrate workflows as **connected nodes**, each node performing a discrete operation or logic step.

Instead of writing code from top to bottom, you build a graph (or flow) of nodes - giving you the same flexibility and control over your **data analysis**, **ETL**, and **reporting** workflows as traditional process functions, but with a far more intuitive and visual interface.

### Why Visual Processes?

* **Clarity & transparency**: The flow of data and logic is explicit and visual, making it easier to reason about, debug, and evolve.
* **Composable logic**: Each node encapsulates a single function or action - linking nodes lets you build complex behavior by composition.
* **Reusability & modularity**: Visual processes can be reused in multiple processes, enabling standardization of logic.
* **Dynamic execution control**: You can branch, retry, throttle, loop, or conditionally route flows - all visually - without embedding complex control logic in code.
* **Lower barrier for non-coders**: Users can understand and assemble flows without having to learn how to code.
* **Expandable** - When advanced logic is needed, or MODLR doesn't support something out of the box that you may require, you can extend your visual processes with **custom code**, combining the simplicity of visual design with the full power of scripting.