CalDAV, Apple iCloud, Zoho and other calendars
Besides Google Calendar and Microsoft / Outlook, 42min connects to calendars that speak CalDAV: Apple iCloud, Yahoo, Fastmail, Zoho, Yandex, and self-hosted servers such as Nextcloud, Radicale, Baïkal, or Synology. You connect them from Availability → Calendar, or from the matching card on Integrations.
These connections use a username and an app password rather than a sign-in redirect — there's no "Sign in with Apple/Yahoo/…" step.
What you can connect
| Provider | Sign-in name | Password |
|---|---|---|
| Apple iCloud Calendar | Your Apple Account email | App-specific password |
| Zoho Calendar | Your Zoho email | App password |
| Yahoo Calendar | Your Yahoo email | App password |
| Fastmail Calendar | Your Fastmail email | App password |
| Yandex Calendar | Your Yandex email | App password |
| CalDAV connection | Whatever the server expects | The account's normal password |
Zoho also asks which
data center region your account lives in —
calendar.zoho.com, .eu,
.in, .com.au, .jp, or
.com.cn. Pick the one you use; 42min only ever
talks to that region.
CalDAV connection is the generic option for
any other server. It asks for a
Server URL (for example
https://caldav.example.com/dav/) in addition to
your credentials. The server must be reachable from the
internet over HTTPS.
What it does
- Reading busy times — the calendars you tick for conflict checks are removed from your booking pages, exactly as with Google or Microsoft.
- Writing events back — new bookings are created on the calendar you set as the write target.
-
No calendar invitations — the event lands
on your calendar, but the calendar server doesn't
email its own invite. Your invitee still gets the 42min
booking confirmation by email, with the
.icsattachment. - No video links — Google Meet and Microsoft Teams ride on a Google or Microsoft connection, so they aren't available here. Use a meeting type of Zoom, phone, in person, or a custom URL instead.
Your credentials are stored encrypted.
How to do it
- Create an app password in your calendar provider's account settings. The connect dialog links to the provider's own instructions.
- Open Availability → Calendar and click Add Calendar, then pick your provider from the list.
- Enter your username or email and the app password. For Zoho pick your region; for a generic CalDAV connection enter the Server URL.
- Click Connect, then choose which of that account's calendars check for conflicts and which one bookings are written to.
You can connect more than one account, and mix these with Google and Microsoft accounts.
Provider notes
- Apple iCloud. Changing your main Apple Account password revokes all app-specific passwords, including the one you gave 42min — you'll need to create a new one and reconnect.
- Zoho. Zoho only shares your default calendar with calendar apps. Events in your other Zoho calendars won't be seen, so keep the meetings you want protected on the default one.
Common issues
- "The server rejected the username or password." Use the app password, not your normal account password — the branded providers won't accept the latter over CalDAV. If you just rotated your account password, generate a fresh app password.
-
"No CalDAV support was found at this address."
For a generic CalDAV connection, the Server URL points
somewhere that isn't a CalDAV endpoint. Check your server's
documentation for its DAV path (often
/dav/or/remote.php/dav/). - "The calendar server could not be reached." A self-hosted server behind a VPN, on a private IP, or on a non-standard port can't be reached by 42min. It needs a public HTTPS address on port 443.
- "Too many attempts." Connection attempts are rate-limited — wait a minute and try again.
- Connected, but slots are still wrong. Connecting the account isn't enough; tick the calendar that actually holds your events for conflict checks.
- Credentials stopped working. Click Reconnect on the account and enter your credentials again. Conflict checking resumes once the connection is repaired.
- Disconnecting. Removing the account stops conflict checking and write-back; booking events already written to your calendar stay there.
Last updated July 19, 2026.