Search documentation

Search docs pages by title or description

Join the waitlist
Browse documentation

Calendar block

Data view

The calendar block plots records by date across four modes — month grid, week, 3-day, and agenda list. It handles multi-day spans, recurring events, and can merge several tables into one color-coded calendar.

Try it: Step through months with the arrows, switch between Month, Week, 3-day, and Agenda, and click an event to open it.
Schedule
March 2026
Meetings Events
Sun
Mon
Tue
Wed
Thu
Fri
Sat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1
2
3
4
Example. A calendar block with two sources: a Meetings table (the weekly stand-up is one row with FREQ=WEEKLY;BYDAY=TU as its recurrence rule, the invoice run one row with FREQ=MONTHLY;BYMONTHDAY=26) and an Events table in blue, where the trade show spans two days through its End field. Week starts on Sunday.

When to use it

  • Bookings, shifts, deadlines, editorial calendars — anything scheduled.
  • Recurring commitments: a weekly stand-up stored once as a recurrence rule.
  • Combined views, e.g. one calendar for the Meetings and Deadlines tables.

Settings

SettingWhat it does
Title fieldThe event label.
Start fieldWhen the event begins. Required.
End fieldOptional end — events span days when it differs from the start.
Recurrence rule fieldOptional column holding an iCalendar RRULE string, e.g. FREQ=WEEKLY;BYDAY=MO — the event repeats accordingly.
Recurrence exceptions fieldOptional column of dates to skip in the recurrence.
Default modeThe mode the calendar opens in; viewers can switch.
Week starts onFirst column of the month and week grids.
Extra sourcesAdditional tables plotted on the same calendar, each with its own title/start/end fields, accent color, filter, and click target.
Event clickThe record page an event opens when clicked.

Like every block, this one also has the shared block settings: a title and optional description, a header you can show or hide, auto-height, conditional visibility, and role-based visibility, plus the source table and record-filter settings shared by all data blocks.