List · reads checkin

Check-ins

Attendance events.

One row per item, the plainest possible view.

Build an agent that makes this All page types

To-do list

Confirm dietary requirementsDue tomorrow
Send quote to MarchandDue Friday
Order langoustinesIn progress
Book second serverNot started

How it works

1
Items are listed newest first unless a sort is set.
2
Each row shows its title and the two or three fields that matter.
3
Filters narrow it without leaving the page.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

Who uses this page

Conference organiser

Handles attendee questions at scale and keeps the programme, speakers and venue straight.

Questions

What data does the Check-ins page use?

It reads checkin records the agent has collected. Attendance events. 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 list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

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.