Calendar · reads event
Events
Everything the agent schedules — dates, place, attendees.
Everything with a date, laid out on a month or week grid.
Fri 12 Sep — Autumn tasting
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Written to be read by strangers, so each entry carries a place and a capacity rather than only a time.
Marking one full stops the agent taking bookings for it, rather than only greying out a button.
The next few dates stay on the site without anyone editing a page.
How it works
- 1
An event is published with a date, a title and a place; the agent starts offering it immediately.
- 2
Places left is decremented as bookings are recorded, where Bookings exists.
- 3
Marking one Full stops the agent taking bookings for it rather than only greying out a button.
- 4
Past events drop off the public list and stay in the record.
Best for
Anything where "when" is the first question.
Not the right choice for
Work with an order but no dates — a board reads better.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Daterequired | date | The published date. Written for a stranger, so a weekday name is included. |
| Eventrequired | text | The title as it should appear publicly. |
| Venuerequired | text | Where. Required, because a public date without a place generates an email. |
| Places left | text | Capacity remaining, or Full, or Drop in. Text because all three are real answers. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- No ticketing or payment. Registration is a conversation, or an external link.
- Capacity is a number the owner maintains unless Bookings is present to decrement it.
- One venue per event, so a roadshow is several rows.
- No waiting list — a full event turns people away rather than capturing them.
Before it works
What you have to provide, if anything.
- Nothing required beyond a date and a place.
- Bookings makes the capacity self-maintaining; without it, Places left is manual.
In practice
A gallery running a programme of tastings and workshops.
“Beginners workshop on the twentieth is full.”
What the agent built
The entry marked full, and the agent instructed to offer the October date instead.
What changed
Enquiries for the full session stopped becoming disappointed emails and started becoming bookings for the next one.
Better with
These do a different job on the same data. An agent can have all of them.
The business runs on appointments or dated commitments and someone needs to see the shape of the month rather than a list.
Customers reserve time, capacity is finite, and double-booking would be a real problem.
Attendance is recorded per session and no-shows matter for planning, billing or certification.
Who uses this page
Non-profit or association
Answers members and donors, and captures the offers of help you would otherwise miss.
Musician or band
Answers booking enquiries with the details a promoter actually needs.
Author or writer
Answers readers, handles event enquiries, and keeps your research where you can find it.
Club or community organiser
Answers members, takes sign-ups, and keeps fixtures and subs straight without a committee.
Questions
What data does the Events page use?
It reads event records the agent has collected. Everything the agent schedules — dates, place, attendees. 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 calendar the wrong choice?
Work with an order but no dates — a board reads better. It is best for: anything where "when" is the first question.
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.
More in Planning & time
4 Sep — Tasting — Maison Lauret
Calendar
Month/week view across all dated nodes.
07:30
Load in, unlock the hall
45m
08:15
Floor plan and chairs
1h 30m
09:45
Sound check
30m
10:30
Doors
—
Planning / schedule
A run-of-show / agenda timeline.
Gantt chart
Tasks & phases with dependencies and durations.
Q3
Custom domains
Shipped
Q3
Module library
Shipped
Q4
Team accounts
In progress
Q1
Public API
Planned
Roadmap
Milestones across quarters/phases.
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