Timeline · reads trip

Travel plan

Segments of a journey.

A run of events in order, along a single line.

Six days on one screen. The per-day detail belongs in an itinerary, not here.

14–16 Oct

Lyon

TGV 06:52 from Gare de Lyon

16–18 Oct

Turin

Train, 4h, change Chambéry

18–20 Oct

Milan

Train, 1h50

20 Oct

Return

Flight MXP–CDG 19:40

How it works

  1. 1

    Dated items are sorted and spaced by how far apart they actually are.

  2. 2

    Gaps stay visible, so an empty fortnight looks like an empty fortnight.

  3. 3

    Each entry expands in place for its detail.

Best for

A schedule someone reads top to bottom — a run-of-show, an itinerary.

Not the right choice for

Comparing parallel workstreams; that is a Gantt.

Questions

What data does the Travel plan page use?

It reads trip records the agent has collected. Segments of a journey. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a timeline the wrong choice?

Comparing parallel workstreams; that is a Gantt. It is best for: a schedule someone reads top to bottom — a run-of-show, an itinerary.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

🏪
Find Providers
👤
Profile
FAQ