The timeline block turns rows into a chronological story: each record becomes an event on a vertical rail, positioned by a date field and grouped under day headers (or year headers when the events span years).
Try it: Flip the rail between oldest first and newest first, toggle the detail cards, and click an event (or its card link) to open its record.
Settings
Activity
Mar 4, 2026
Owner
MKMara Koenig
Tags
QuoteQ-2291
Notes
Sent the revised quote with the volume discount the buyer asked for.
Owner
JLJonas Lind
Tags
Call
Notes
Buyer wants delivery before the end of the quarter; follow up Friday.
Mar 6, 2026
Owner
MKMara Koenig
Tags
OrderPO-118
Notes
Purchase order received from Nordic Supply AB and booked.
Mar 9, 2026
Owner
JLJonas Lind
Tags
Logistics
Notes
Pallet pickup confirmed for Thursday morning.
Example. A timeline block over an Activity table. The Occurred at datetime field positions each event: the headline carries the date and how long ago it happened, the rail connects the dots, and ticking card rows (Owner, Tags, Notes here) adds a detail card with a link to the record under each entry.
Positions and orders the events. Required — publishing checks it's a real date or datetime field.
Order
oldest first / newest first
Rail direction. Defaults to oldest first.
Time ago
on / off
Prints how long ago each event happened beside its date ("4 hours ago", "yesterday"). On by default.
Card rows
up to 6 fields
Fields listed as label/value rows on a detail card under each event, in the table's field order. People, chips and paragraphs render as they do on a record page.
Row click
record view
The record page an event opens when clicked. With card rows on, the card also gets a footer link to it.
Card link
text
The footer link's label. Defaults to "Open record".
Rows whose date field is empty are left off the rail — give the timeline a required date field if every record must appear.
Like every block, this one also has the shared block settings: an optional title (which shows as a heading above the block) with a description under it, auto-height, conditional visibility, and role-based visibility, plus the source table and record-filter settings shared by all data blocks.