Google Calendar invite link: when a link beats a formal invite

Somebody needs to be at a meeting, and the obvious move is to type their email address into the guest field. Then the reason for looking for a link appears: the address is unknown, or the group is too large to list, or the event needs to sit on a public page where anyone can pick it up. Google Calendar answers all three, but not with one mechanism. There are three different things people mean by an invite link, they behave differently, and picking the wrong one produces an event that nobody can see or one that everybody can change.

The three things called an invite link

The first is a guest invitation. Adding an email address under Guests sends that person a mail with Yes, No and Maybe links in it, and Google's documentation is clear that this works for anyone with an email address, whether or not they use Google Calendar. This is not a link in the usual sense. It is addressed mail, and the recipient is on the guest list before they answer.

The second is a published event link. On an event that sits on a public calendar, the More actions menu offers Publish event, and that window hands over two things: a link that anyone can open to see the time, date and description, and HTML code for an add-to-calendar button that can be pasted onto a web page. Nobody who opens it joins the guest list.

The third is a booking page. An appointment schedule produces a page where other people choose a slot, and the event is created when they book rather than being created first and advertised second.

What it is Who ends up on the guest list Needs a public calendar
Guest invitation The invited address, immediately No
Published event link Nobody, unless they are invited separately Yes
Booking page Whoever books a slot No

The distinction that matters is the guest list, not the delivery. Almost every problem with invite links traces back to treating a link that only displays an event as though it had invited someone.

What the published link requires, and what it breaks

Publish event has a precondition that is easy to miss: the event has to be on a calendar that has been made available to the public. That setting lives in the calendar's own settings under access permissions for events, and it has a companion option to show only free and busy information while hiding details, which would defeat the purpose here. Google notes that removing public sharing usually takes a few minutes but can take up to four hours to take effect, so a calendar made public for one event is not instantly private again afterwards.

The published link also carries a documented limitation that decides where it can be used. Google states plainly that links from the Publish event feature work best on desktop web browsers, and that opening one in the Google Calendar app on a mobile device may fail to load the event details or show a blank event. The suggested workaround is to open the link in a browser and save the event from there.

That single line rules the feature out for a lot of real uses. A link pasted into a chat message will be opened on a phone by a good share of the people who receive it, and a blank event is worse than no link. Where it earns its place is a web page, a newsletter, or anywhere the reader is at a desk, and where the add-to-calendar button can sit next to it as the actual call to action.

The whole-calendar links are a different set

Sharing an entire calendar rather than one event uses different links, and they are worth knowing so they are not confused with an event link. A shareable link lets people subscribe in Google Calendar. A public URL to the calendar gives access in a browser with no sign-in and no subscription. A public address in iCal format is the one other calendar applications can consume, and it works only while the calendar is public.

What a guest invitation does that no link can

For anything with a guest list, the ordinary invitation is not the fallback. It is the feature, and several of its behaviours have no equivalent in a link.

Responses come back. Guests answer with the Yes, No or Maybe links in the mail, the organizer is notified, and the event on the calendar shows who is attending and their status. A published link produces nothing of the kind.

Availability is visible while the event is being built. Find a time shows when invited guests can attend, for guests who have shared their calendar or who are in the same organization, and guests in other time zones have their local start time shown under their name. Google's troubleshooting note on this is worth carrying: suggested times are based on guest availability and working hours, so someone whose working hours are set incorrectly will get poor suggestions.

The invitation can arrive without landing

One behaviour sits between the two mechanisms and catches people out. Google's guidance notes that when the organizer is not in the same organization as a guest, or the guest has never interacted with them before, the guest may have to respond to the email invitation before the event appears on their calendar at all. The recommendation attached to it is to remind the guest through whatever channel they actually read, asking them to click Yes or Maybe.

That is the situation people usually try to solve with a link, and a link is the wrong instrument for it. The event was delivered. It is waiting behind an answer. Sending the same person a published event link adds a second artifact that also does not put the meeting on their calendar, and now there are two things to explain.

There are also hard ceilings. Up to 200 people can be invited to a single event. Beyond that the route is Google Groups, which can reach groups of up to 100,000 people. The group chat that Calendar can open for an event has the same 200-guest ceiling including the organizer, external guests are not added to it, and the feature exists only on work and school accounts.

Forwarding is the link that already exists

Before building anything, there is a plainer answer for the case of one extra person: forward the invitation mail. Anyone with permission to add guests can forward an invite, and when the new guests respond they are added to the guest list and can invite others in turn.

This is convenient and it is not free. Google's own warning is specific: a recipient of a forwarded invitation might be able to see updated meeting details and could change the RSVP response at any time. The response being changed is the organizer's own guest entry, which is a sharper consequence than most people expect from forwarding an email.

The control for it is on the event, under what guests can do, where the option to invite others can be unchecked. The Calendar API documents the same field and its default, and the default is the permissive one: attendees other than the organizer can invite others unless that is switched off. Seeing who else is on the list is also on by default. Neither default is wrong, but neither is a decision either, and for an interview or a salary conversation both should be made deliberately.

When a booking page is the right shape

For the case where the other person should choose the time, a link is genuinely the better tool, and an appointment schedule is the feature built for it. It produces a page under a title that is visible to anyone holding the link, and the event appears once a slot is taken.

The setup carries a set of limits that are worth reading before committing to it. An appointment schedule can be created on a personal Google Account or a Workspace account, but only on a computer, since it cannot be created in the Calendar app on Android, iPhone or iPad. Some features require an eligible Google Workspace or Google One subscription. By default there is a four-hour minimum lead time, which is why a booking page checked immediately after being set up often shows nothing available for the rest of the day.

Several settings prevent the predictable problems. Buffer time puts space between appointments. A maximum bookings per day figure caps the load. Requiring email verification sends a code to people who are not signed in to a Google Account, which is the answer to spam bookings. Up to five reminders can be sent, though the text of those reminder emails cannot be edited. One default is worth changing on day one: co-hosts can be added, and their calendars are not checked for availability unless that is turned on.

Question Guest invitation Published event link Booking page
Who picks the time Organizer Organizer The other person
Works on a phone Yes Unreliable in the Calendar app Yes
Created from mobile Yes No No
Suits an unknown audience No Yes Yes

The link that always exists but is not for sharing

Every event has a canonical web address. The Calendar API exposes it as htmlLink, documented as an absolute link to the event in the Google Calendar web interface, and marked read-only.

It is worth naming because it is the link people copy out of the browser address bar and paste into a message, expecting it to work like an invitation. It does not invite anyone, and it does not grant anyone access. A recipient who is not on the guest list and does not have access to the calendar gets nothing useful from it. Sharing an event with someone who is not invited is exactly the job that Publish event exists for, and the address bar is not a shortcut to it.

The practical version of all this is that an event with guests should be built with guests, and the link forms should be reserved for audiences that cannot be enumerated. Getting the guest list right in the first place is faster when the whole week is in front of the person doing it, with times and travel visible while the invitation is being written rather than after it has gone out, and the Guide covers how events and their guests get entered in one pass.

What to change first

Open the event that keeps generating link problems and decide which of the three shapes it really is: a guest list, a public announcement, or a slot someone else should pick. Then check the guest permissions on it, since the default lets attendees invite others and see the full list. If the awkward part is building the event in the first place, a Mac calendar that keeps the week and the guest list on one screen, such as Caltimate, is worth a look.

Frequently asked questions

How is a Google Calendar invite link different from adding a guest?

Adding a guest puts that address on the event immediately and sends mail with Yes, No and Maybe links, so responses come back and the organizer can see who is attending. A published event link only shows the event details to whoever opens it, and nobody who opens it joins the guest list or can respond.

Why does the link from Publish event show a blank event?

Because the event was opened in the Google Calendar mobile app rather than a browser. Google documents that Publish event links work best on desktop web browsers and that on a mobile device the details may fail to load or the event may appear blank, with the recommended workaround being to open the link in a browser and save it from there.

Can an invite link be created without making the calendar public?

Not the Publish event link, which requires the event to be on a calendar that has been made available to the public. For a private calendar the options are inviting guests by email address, forwarding the invitation to someone who should be added, or using an appointment schedule booking page, none of which require the calendar to be public.

What happens if someone forwards a calendar invitation?

The new recipients can respond and are added to the guest list, and they can invite others in turn. Google also warns that a person who receives a forwarded invitation might see updated meeting details and could change the RSVP response at any time, which is why the option letting guests invite others can be unchecked on the event.

How many people can be invited to one Google Calendar event?

Up to 200 people can be invited directly. For a larger audience the documented route is Google Groups, which supports groups of up to 100,000 people, and the group chat Calendar can open for an event is also capped at 200 guests including the organizer.

Back to all posts