Calendar views
- How any custom type can be displayed as a calendar
- When a type gets a calendar view and how to open it
- How the Agenda template uses calendar views for appointments
- How recurring entries work
In AutoTalk a calendar is a way to view a custom type — not a separate built-in app. Any custom type whose records carry a Date or Date & time field can be shown on a calendar, so you can browse and manage those records by day, week, or month instead of as a flat list.
When does a type get a calendar?
A custom type shows a calendar view when its definition includes a calendar configuration — at minimum, which date/date-time field marks the start of each entry. You can also point it at an end field, a title, a color, and a recurrence field.
Once a calendar is configured, the type gains a calendar view next to its normal list view, reachable from that type's entry in the sidebar. Types without a date field — or without a calendar configuration — appear as a list.
The Agenda template
The quickest way to get a working calendar is the Agenda onboarding template. When you create a company with the Agenda template, AutoTalk provisions a set of ready-made custom types for appointment scheduling:
| Type | What it holds |
|---|---|
| Events | The appointments themselves — date/time, who, and what |
| Services | Bookable services, each with a duration and price |
| Working Hours | Each employee's normal weekly schedule |
| Employee Periods | Time off and one-off availability overrides |
Events ships with a calendar configuration already in place, so it opens directly as a calendar. This is the same mechanism you can add to any custom type — the Agenda template is just a pre-built example tuned for bookings.
The calendar views
A calendar offers four ways to look at the same records:
- Day — a single day, hour by hour. Best for a detailed look at one day's entries.
- Week — the current week across all working hours. Good for spotting gaps and overlaps.
- Month — a full month at a glance. Good for an overview.
- Agenda — a chronological list of upcoming entries.
Use the navigation arrows to move between periods, and filters to narrow down which records are shown (for example, by the employee an Event is assigned to).
Creating an entry from the calendar
Using the Agenda template's Events type as the example:
- Navigate to the date with the arrows or by switching views.
- Click a time slot (Day/Week view) or a date cell (Month view) to start a new Event.
- Fill in the record's fields. For Events these are the contact, the service(s), the assigned employee, and the start/end time — but the form always reflects whatever fields your custom type defines.
- Save. The entry appears on the calendar immediately.
You can open any entry to edit it, drag it to a new slot to reschedule, or delete it. For Events, the end time and title can be filled in automatically by the Agenda template's workflows (for example, computing the end time from the selected services' durations).
Recurring entries
If the calendar configuration declares a recurrence field, entries can repeat on a schedule instead of being re-created by hand. Recurrence is stored as a standard RRULE string, so a type can express daily, weekly, or monthly patterns (for example, a weekly session every Tuesday at 10:00).
A recurring entry is stored as a single record, and the calendar expands it into one event per occurrence in the visible range. Editing it edits that one record, so a change applies to the whole series rather than to a single occurrence.
How records connect (Agenda example)
In the Agenda template, each Event links three other records together:
| Field | What it answers |
|---|---|
| Contact | Who is the appointment for? |
| Service | What is being done? |
| Employee | Who is providing it? |
The Contact is a real contact record, so an Event references the contact rather than copying their details. The Agenda template's workflows also stamp a lastScheduledEventAt timestamp onto the contact (used, for example, to follow up after a period of inactivity); the appointments themselves are not listed on the contact's profile. This three-way link is specific to the Agenda template's design; your own calendar-enabled types can reference whatever records make sense for them.
Next steps
- Creating a Custom Type — define a type and its fields, including Date / Date & time fields
- Managing records — add, edit, and filter records
- Using Custom Types with AI agents and MCP — let agents read and write calendar records