Otto connects via CalDAV or, for Microsoft accounts, via its own Microsoft Graph connection — and estimates travel time between appointments on the device, without any address ever leaving it.
Contents
Docs overviewCalendar · Appointments & travel time
Ten tools, two connection paths
Everything Otto does in the calendar runs through one of ten tools — from viewing to cancelling. It connects through your own calendar service, never through a second, separate calendar.
The ten tools
- View
- Appointments for a range; without one, the coming seven days, from every calendar of one account.
- Search
- By keyword in title, location and description; without a date range, 60 days back, 400 days forward.
- Find free slots
- Accounts for existing appointments, quiet hours and estimated travel time; searches at most 14 days ahead, usually three suggestions.
- Create
- Also multi-day or all-day, targeted at a specific calendar, with real invitations when addresses are given.
- Edit
- Title, location and notes of an existing appointment — for a single occurrence or the whole series.
- Move
- Changes time and duration; with invitees, the appointment then shows as “moved, unconfirmed” until everyone has accepted.
- Cancel
- Removes the appointment at the calendar service and notifies invitees — final, cannot be undone.
- Invite
- Adds further people to an existing appointment.
- Respond
- Accepts, declines, or tentatively responds to an invitation on your behalf.
- View calendar status
- Lists connected accounts and their individual calendars, including the default one.
Two connection paths
-
CalDAV
Apple Calendar, Google, Nextcloud, mailbox.org, Synology and every other standard calendar service.
-
Microsoft Graph
A separate, dedicated connection — Microsoft never offered CalDAV, so a Microsoft calendar never runs over the CalDAV path.
The estimated travel time
Before Otto proposes a free time, it estimates the drive in between — on your device, from straight-line distance and a detour factor, without any address ever leaving the device. An estimate is not a route: it knows neither a traffic jam nor roadworks. If the location is unknown, Otto does not calculate; it keeps a fixed 15-minute buffer free instead.
Known gaps in this documentation build (as of 25 Sept 2026)
- The Microsoft Graph write paths (creating an appointment, checking RSVPs) are built in, but not covered by their own automated test — unlike the thoroughly tested equivalent CalDAV path.
- Co-connecting a Nextcloud calendar is likewise without its own automated test.