Status Timeline
Status Timeline
Status Timeline
What you get
Capability
Maker setup
End-user result

Before you start
Step 1 — Add Status Timeline
Step 2 — Preview across statuses
Checklist
Troubleshooting
Symptom
Likely cause
Fix
Show a horizontal Status Timeline on Details so users see where a record sits in its Status lifecycle (past → current → upcoming options).
What changed A new view component, Status Timeline, binds to a Notion Status property and renders options in order with the active status highlighted. It is read-only display — use Board drag, Update Form, or multi-row update to change Status.
Lifecycle strip
Add Status Timeline, bind Status field
Options in a horizontal progress-style row
Active marker
Automatic from record value
Current status emphasized
Option order
From Notion Status options
Matches Notion’s configured order

A Notion Status property with the options you care about
A Details screen
Reload Data after editing Status options in Notion
Open the Details screen.
Add component → Status Timeline.
Bind it to the Status property.
Optionally set a label (for example Status Progress).
Open records in different statuses (Not started, Scouting, Open, Closed).
Confirm the timeline highlights the correct active option each time.
Publish and re-check in the live app.
Missing options
Stale sheet metadata
Reload Data
Wrong active step
Record Status empty or different property
Bind correct Status field
Want to edit on the timeline
Component is view-only
Use Board DnD or Update Form
Board List View — change Status by dragging columns
This guide teaches a focused maker workflow. For the full screen option inventory (What it does / How to use / Why) and annotated builder screenshots, use the matching Types of Screens guide:
Data screens: List (View Items), Details, Form (Add Item), Form (Update One Item), List (Update Items), Content
Everyday chrome / Queue & activity: see the Types of Screens index
Automation native screens: Native Automation Screens
Change one option family at a time, then publish and test on phone and desktop.
Prefer screen-level settings in Content / Behaviour / Appearance before custom CSS/JS.
Keep public access and navigation visibility intentional on every screen you link from this guide.