Why does 42min ask for an app-specific password instead of a “Sign in with Apple” button?

Apple doesn't offer a calendar sign-in flow the way Google and Microsoft do. Calendar access to iCloud goes through CalDAV, which authenticates with a username and password, and Apple's answer for third-party apps is the app-specific password — a separate credential you generate yourself and can revoke on its own without changing your Apple Account password.

Is an app-specific password safe to give 42min?

It's the mechanism Apple built for exactly this. It's a distinct credential from your Apple Account password, it can be revoked individually from account.apple.com at any moment, and revoking it cuts 42min's access without affecting anything else on your Apple Account. 42min stores it encrypted and only ever sends it to Apple's calendar servers.

Does my invitee get an invitation from Apple Calendar?

No, and that's deliberate. 42min writes the event to your calendar without attendee lines, so Apple's servers never send an invitation of their own. Your invitee gets 42min's booking confirmation by email with an .ics attachment they can add to any calendar. The upside is that nobody receives two invitations for one meeting; the thing to know is that the event on your iCloud calendar isn't tracking anyone's RSVP.

My iCloud connection stopped working after I changed my Apple password.

That's expected. Changing your main Apple Account password revokes every app-specific password on the account, including the one you gave 42min. Generate a fresh app-specific password and click Reconnect on the account in Availability → Calendar. Conflict checking resumes as soon as the connection is repaired.

Which calendars should I tick for conflict checks?

The ones that actually hold the events you don't want booked over — usually your main calendar, plus anything personal you'd rather protect. Connecting the account is not the same as choosing its calendars: an account can be connected and healthy while the calendar holding your meetings is still unticked, which is the single most common reason slots look wrong.

Can I connect iCloud alongside a work Google or Outlook calendar?

Yes. Connect as many accounts as you like, from the same provider or different ones, and set conflict checking per calendar. A common setup is a work Google account and a personal iCloud account both checked for conflicts, with bookings written to the work one — so a school pickup on your iPhone closes a work slot without any work meeting ever landing on your personal calendar.

What happens if Apple's servers can't be reached?

42min falls back to the busy times it last read successfully, for up to twenty minutes. After that it stops guessing: the account is treated as unavailable rather than free, and its slots are withheld. You may see fewer bookable times during an outage, which is the deliberate trade — an unreadable calendar is never assumed to be empty.

Why can't I choose one of my calendars as the write target?

42min only offers calendars it has confirmed it can write to. Subscribed calendars, shared calendars you have read-only access to, and holiday calendars fall outside that, so they can be used for conflict checking but not for creating bookings. If nothing is offered, pick or create a calendar you own in Apple Calendar and refresh the account.

Does 42min touch events I created myself?

No. 42min only ever reads your own events, and only writes, updates or removes the events it created for bookings. Anything you made in Apple Calendar is left exactly as it is.

What happens to my meetings if I disconnect iCloud?

Disconnecting stops conflict checking and write-back from that point on. Booking events already written to your iCloud calendar stay there — nothing is cleaned up or removed retroactively, so your existing meetings keep their place in your schedule.

Can a whole team share one booking link if we're on iCloud?

Yes. Round robin, group and routing-form event types don't care which calendar provider each host uses — every teammate connects whichever calendar their meetings live on, iCloud or otherwise, and 42min pools their availability behind one link.

How to connect Apple iCloud Calendar

The calendar on your iPhone becomes the one that decides what people can book. 42min reads it for conflicts, writes every new booking back to it, and — when Apple can't be reached — withholds slots rather than guess.

Connect iCloud to 42min →

No credit card · Free plan · Every feature unlocked

What the iCloud connection does

The connection runs in both directions — 42min reads what's already on your Apple calendar, and puts what gets booked back onto it.

Busy times

READ

Every calendar you tick for conflict checks is subtracted from your booking page. A dentist appointment on your iPhone closes that slot to invitees without you touching 42min.

New bookings

WRITTEN BACK

Each confirmed booking is created as a real event on the calendar you choose as the write target, so it's on your Mac, iPhone and Apple Watch the moment it's made.

Reschedules and cancellations

FOLLOWED

Moving a booking moves the event; cancelling it removes the event. Delete one by hand in Apple Calendar and a later reschedule recreates it rather than losing the meeting.

Recurring events

EXPANDED

Repeating events are worked out occurrence by occurrence, so a weekly stand-up blocks every week — not just the first one.

Connect iCloud in 3 steps

About five minutes, most of it spent on Apple's site generating the password.

Create an app-specific password

Sign in at account.apple.com, open Sign-In and Security → App-Specific Passwords, and generate one for 42min. Copy it — Apple shows it once. This is what you'll enter in 42min alongside your Apple Account email; your normal Apple password won't work here.

Add the calendar in 42min

Open Availability → Calendar, click Add Calendar, and pick Apple iCloud Calendar from the provider list. Enter your Apple Account email and the app-specific password, then click Connect.

Choose what each calendar does

Tick the calendars that should check for conflicts, and pick the one new bookings are written to. This step is the one people skip, and it's the one that actually protects your time.

The 'Connect Apple iCloud Calendar' dialog in the 42min dashboard, with Username or email and App password fields — The connect dialog. “How to create one” opens Apple's own app-password instructions, and the notes under the fields spell out what the connection will and won't do.

The same dialog handles Yahoo, Fastmail, Zoho, Yandex and self-hosted CalDAV servers such as Nextcloud or Radicale — full reference in the CalDAV and Apple iCloud help guide.

iCloud alongside everything else

iCloud isn't an either/or. Connect as many accounts as you like, from the same provider or different ones, and decide per calendar what each is for. The setup most people end up with: a work Google or Microsoft account for bookings, and a personal iCloud account checked for conflicts only.

The effect is that your private life protects your work calendar without ever being exposed to it. A dentist appointment on your iPhone closes that afternoon slot; the client who books the next one never sees why, and nothing about the meeting they book lands on your personal calendar.

What your iCloud calendar can carry

Nothing in 42min is gated on which calendar provider you use. Once iCloud is connected, every event type behaves the same as it would for a Google or Microsoft user — and on a team, hosts can be on different providers entirely without anyone having to standardize.

Round robin pools your team's availability behind one link and assigns each booking to whoever has had the fewest recent meetings — reading each host's own calendar, iCloud or otherwise.
Group events let many invitees book the same slot, with a seat cap that closes it when full.
Routing forms ask a few questions first and send each visitor to the booking page that fits.
Meeting polls find a time that works for a group. While the vote is running, 42min places tentative holds on the candidate times on your write-target calendar, so a slot everyone is voting on can't be quietly booked out from under them.

Round robin flow: one team link, a shared availability grid across four teammates, and the booking assigned fairly

When iCloud won't connect

“The server rejected the username or password.” Nearly always the normal Apple Account password being used instead of an app-specific one — Apple won't accept it over CalDAV. Generate an app-specific password and try that.

It worked yesterday and now it doesn't. Check whether your Apple Account password changed. Apple revokes every app-specific password when it does, silently and without warning 42min. Generate a new one and use Reconnect.

“Too many attempts.” Connection attempts are rate-limited to make guessing credentials pointless. Wait a minute and try again.

Connected, but slots are wrong. Tick the calendar that actually holds your events for conflict checks. Connecting the account doesn't select anything on its own.

Bookings aren't reaching Apple. Set a write target. Without one, 42min has nowhere to create the event — the booking is still confirmed, it just doesn't appear on your calendar.

Disconnecting doesn't rewrite the past. Removing the account stops conflict checking and write-back going forward; events already written to your calendar stay exactly where they are.

Apple iCloud Calendar FAQ

Yes. Apple iCloud Calendar is a supported calendar connection on every plan, including the free one. You connect it from Availability → Calendar with your Apple Account email and an app-specific password. Once connected, 42min removes your busy times from your booking page and writes each new booking back to the iCloud calendar you choose.

Your Apple calendar, behind your booking link

Connect iCloud once and stop checking your phone before you say yes to a meeting. Free, with no per-seat bill.

Create 42min account →

No credit card · Free plan · Every feature unlocked