ReferenceComponents
timeline
Planned things in time order: an agenda, an itinerary, a schedule.
What happens when. timeline lays out planned things in time order — tomorrow's classes, a trip's legs, a week of training, medication times — under day headings when it spans days.
Tomorrow09:30PhysicsRoom 20411:00Linear algebraHall B14:15Study groupLibrary, 3rd floor
Re-rendered in the browser from the SDK’s own scales. Not a screenshot.
When not to use it
What already happened is item_list; the progress of one order or claim is order_tracker. There is no hour grid: on a phone it does not fit.
Props
Every block also carries type and a required fallback_text of 1 to 300 characters.
| Prop | Type | Required | Constraints |
|---|---|---|---|
title | string | No | Up to 80 characters. |
groups | array | No | Up to 7 entries. |
groups[].label | string | Yes | 1 to 40 characters. |
items | array | Yes | 1 to 16 entries. |
items[].group_index | integer | No | 0 to 6. |
items[].time_label | string | Yes | 1 to 24 characters. |
items[].starts_at | string | No | ISO 8601 in UTC (...Z); a numeric offset fails validation. |
items[].ends_at | string | No | ISO 8601 in UTC (...Z); a numeric offset fails validation. |
items[].title | string | Yes | 1 to 80 characters. |
items[].subtitle | string | No | Up to 120 characters. |
items[].icon | string | No | Up to 40 characters. |
items[].action | action | No | { kind: "reply", text } or { kind: "open_url", url } or { kind: "navigate", route } or { kind: "call", phone } or { kind: "copy", text } or { kind: "add_to_calendar", title, starts_at }. See Actions. |