# Work that runs on the board

**URL:** <https://community.beach.io/t/work-that-runs-on-the-board/160>\
**Category:** Canvas\
**Created:** [November 20, 2026, 10:02am UTC](https://community.beach.io/t/work-that-runs-on-the-board/160 "2026-11-20T10:02:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![steve](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.beach.io/steve/32/43_2.png) [@steve](https://community.beach.io/u/steve)\
**Post date:** [November 20, 2026, 10:02am UTC](https://community.beach.io/t/work-that-runs-on-the-board/160/1 "2026-11-20T10:02:34Z")

</div>

Most boards stop at planning. Someone reads the stickies afterwards and writes the summary somewhere else. This thread is about flows, our first step toward that work happening on the board.

A flow starts with connectors. Draw them from the material you want to use into a document or a table, give that target a prompt, and run it. Text from everything upstream becomes the context: stickies, cards, shapes, text, other documents, and tables. A frame counts as one bundle with its title. The result writes into the target as it is generated, so the whole room watches it fill in.

What you can do today:

- Run one step, or run it and every connected step after it, in order
- Pin a result so a later run will not overwrite it. A pinned object still feeds the steps after it.
- Stop a run at any point

When the target is a table, the result arrives as rows in its columns.

The prompt sits on the board, next to the material it reads, so everyone can see what went in and what came out. Stop always wins. If a run stalls, pressing Stop again, or waiting a few seconds, ends it on the board.

This is early, and it is not meant to be a workflow tool. We want to learn which steps teams want to run where they work.

What would you connect into a flow first? When flows open for testing, run one on a real board and tell us what you expected and what you got.
