Skip to main content
KanbanBoard turns any schema table into a drag-drop workflow board. This page explains the props, how rows are grouped into columns, and what happens when a user drags a card. Records become cards; cards are grouped into columns by the value of a single field. You declare which field defines the columns and which fields appear on each card. Dragging a card between columns updates that field on the underlying record. Reach for it whenever you have a workflow with discrete states — task tracking, sales pipelines, content workflows.

​
Example

kanban-board.json
{
  "block": "KanbanBoard",
  "props": {
    "schema_table": "tasks",
    "group_by": "status",
    "columns": ["todo", "in_progress", "done"],
    "card_fields": ["title", "owner", "due_at"]
  }
}

​
Props

​
How it binds to data

On render, the runtime issues a runQuery against schema_table and groups the returned rows by group_by. Each distinct value in columns becomes a swimlane header. Cards whose group_by value is not listed in columns are filtered out — pin every state you want visible to a columns entry. When a user drags a card from one column to another, the runtime writes the new value back to the group_by field on that record.
The drag-write behavior is not fully specified in the available source. Treat the field update as automatic for prototyping, but check the live block schema via the Builder MCP get_block_schema tool before shipping a production board.

​
Patterns

​
Common props

In addition to the KanbanBoard-specific props, every block accepts id, class_overrides, visible_if, and analytics_event. See common props on the PageBlocks overview.

​
Where to go next