Back to all writing

FlowDrop Office: a workflow you can watch

I built a pixel-art office where every node of a FlowDrop workflow is a desk, so anyone can see what a run did.

Explaining an AI workflow is hard. In the editor you see nodes and edges. In the logs you see a list of jobs with ids and JSON. Both are fine for the person who built it. For everybody else, not really.

So I tried something different. What if each node was a person at a desk, and you could watch the file move from one desk to the next?

That is FlowDrop Office.

One brief, from the chat to the draft, walked desk by desk.

Where it comes from

It started as a custom module in a demo site, for one workflow. After a day playing with it, it was clear that nothing in it was about that workflow. It reads the workflow you already have, so it works with any of them. Then it made sense to move it to drupal.org as a contrib module.

I built it with the help of Claude.

How it works

zero setup, promise

You do not configure anything. The office comes from the workflow itself:

  • Every caption node in the FlowDrop editor becomes an office, with the nodes on its right inside.
  • Every other node is a desk. The person at the desk shows what kind of node it is: a robot for AI nodes, a guard for guardrails, a dispatcher for gateways, a clerk for templates and text.
  • When a run is replayed, a clerk finishes at one desk and walks the file to the next one. The camera follows, and a subtitle says what the node did in plain words.

Next to the scene there is an inspector. It tells each step with the real values of the run: what came in, what the node did and why, and what went out. The raw job output is still there for the people who want it.

You can replay any of the last 12 runs, or send a new message from the chat on the page and watch that run. You can also star a run and keep it as a favorite. A favorite plays offline, without the pipeline, the AI provider or the network.11Favorites are stored in the workflow configuration, so they move to another site with a normal config export and import.↩︎ For a live demo this is my safety net.

For people who never saw a workflow

The plain view hides the node names and tells the run in seven stages: Receive, Safety, Understand, Search, Write, Review, Answer. Presentation mode puts the office full screen with the plain view on, and the arrow keys work from a presentation clicker.

There is also a Record button. It replays the run and saves it as a video, so you can share it with somebody who does not have access to the site.

Make your own scene

a hospital? a factory? a castle?

The office is only one way to draw a workflow. The drawing is a scene, and scenes are extensible: anybody can create a new one adapted to their needs.

A module declares its scene in a MODULE.flowdrop_office_scenes.yml file, and its script registers it with Drupal.flowdropOffice.registerScene().22The YAML keys and the scene contract are still internal, so they can change while the module grows.↩︎ The page then lets you switch between the scenes. The replay, the camera, the chat and the inspector stay the same. The scene only decides how the workflow looks.

The module comes with two examples as submodules: a board, an isometric platform with one colored tile per section, and a town hall. So if a pixel-art office does not fit your team or your audience, you can draw something that does.

Things I had to take in mind

Personal data. A live turn runs in a FlowDrop session, and the session stores each message and sends it again as history on later turns. So a guardrail inside the workflow only sees the current message. To mask or refuse a message before it is stored, the module has one hook: hook_flowdrop_office_turn_alter().

Big workflows. An office with 40 desks is not readable. So offices are split at 16 desks, and steps that only pass the file on go by in a blink. If a replay would still take more than about a minute and a half, it plays faster.

Read-only. The office only reads FlowDrop’s own storage. The only thing it writes is the sessions of the live turns.

Try it

It needs Drupal 11.3 and FlowDrop. There is no tagged release yet, so take in mind that things can still change. The documentation explains the installation and every part of the page.

If you try it with your own workflows, let me know what do you think. The issue queue is open.