How to schedule a Google Meet call from your calendar and send the link in one step

There are five places to create a Google Meet call and they do not produce the same thing. A code made on the Meet homepage behaves differently from one attached to a calendar event, expires on a different schedule, and lets a different set of people in. Most instructions treat this as one task with several routes. It is closer to several tasks that happen to share a button.

The decision worth making before clicking anything is whether the meeting has a fixed time and a guest list. If it does, the calendar event is the object that matters and the link is a property of it. If it does not, a standalone link is the right answer and putting it in a calendar event later causes the problems described below.

Creating the link from the calendar event

Google documents the calendar route as part of the event, not as a separate step. Open Google Calendar, create the event or open one you have edit access to, find the conferencing field, and click Add Google Meet video conferencing. Add the guests, then click Save.

Saving is where the link travels. Google's help on inviting people states that guests receive an email invitation and can respond with the Yes, No, or Maybe links inside it, including guests who do not use Google Calendar at all. When an event with guests is edited, Calendar offers to email them, and Google recommends sending those emails so the change is visible rather than silent.

Two details in Google's documentation are worth reading closely, because they explain behaviour that otherwise looks like a bug.

The code belongs to the event. Google states that until it expires, the meeting code is permanently linked to the original Calendar event. Copying an event, or pasting its link into a new one, does not create a second meeting. It points a second event at the first meeting.

The original event's guest list is the access list. Google's wording is that the guest list for the original event controls who can join the meeting and who has access to meeting records such as recordings and chat history. Forwarding the link is therefore not the same as adding a guest, and adding somebody to a duplicated event does not grant them anything.

Notifications are separate from invitations. Google documents up to five notifications per event, and states that those notifications are not shared with Google Calendar guests, who get reminders according to their own settings instead. Guests on other calendar services do receive the notifications that were set.

Where the meeting was created decides how long the link lives

This is the least known part of Google Meet and the cause of most expired code messages. Google publishes the expiry rule per product, and the rules differ substantially.

Where the meeting was created	When the code expires
Google Calendar	After 60 days without use, and only if no future event uses it
Gmail	365 days after last use
The Meet homepage	365 days after last use
Google Chat	365 days after last use
Google Classroom	365 days after last use
Outlook and other third party software	365 days after last use
Breakout rooms	Instantly, once the main meeting ends
Meeting room hardware	Instantly, once everyone leaves
Workspace nicknamed meetings	Instantly, once everyone leaves

Two consequences follow. A recurring meeting created in Calendar keeps its code indefinitely, because a future event is always attached to it. And a code from a third party tool, pasted into a calendar invite, is not treated as a Calendar meeting at all. Google states that in that case the code expires according to the product it came from, which is why some long dormant series break while others do not.

Google also notes that a code used inside the 365 day window gets another 365 days from that moment, so an occasional meeting stays alive as long as somebody joins it.

Choosing between the five starting points

Google lists Meet, Gmail, Google Calendar, Google Chat on mobile only, and other scheduling systems as the places a meeting can begin.

The Meet homepage offers three options behind New Meeting. Create a meeting for later produces a link to keep and share, with no time attached. Start an instant meeting opens the call immediately. Schedule in Google Calendar simply sends you to Calendar, which is worth knowing because it is not a separate mechanism. Google also documents a video call option to add extra encryption, shown as Add encryption by google.com.

Gmail creates a meeting from the left sidebar, with buttons to copy the meeting invite or share it by email, and then a Join now button.

The practical rule is that a meeting with a time belongs in Calendar and a meeting without one belongs on the Meet homepage. A standing link for office hours, pasted into a document, is the second case. A call at eleven on Thursday with four people is the first, and creating it as a standalone link means nobody gets a calendar entry, nobody gets a reminder, and nobody can respond.

Automatic conferencing, and why one event holds only one call

Google Calendar can attach Meet to everything without being asked. In Settings, under Event settings, the option is called Automatically add Google Meet video conferences to events I create. It suits anyone whose meetings are nearly all remote and annoys anyone whose calendar is mostly blocked time and errands, since every dentist appointment arrives with a video link.

There is a firm constraint alongside it. Google states that an event can have only one conference, whether that is Google Meet or another provider's add-on. The failure mode is documented too: inserting conference details directly into the location field or the event description, or using a browser extension, may result in multiple conferences attached to one event. Guests then see two join buttons and split between them.

The clean approach is to use the conferencing field and nothing else. If a different provider is needed, its add-on goes in that same field through the Add conferencing dropdown, which Google says lists conferencing add-ons installed from the Workspace Marketplace.

Who can actually get in, and who has to ask

Access is decided by the account that organized the meeting, not by the link. Google publishes this as a table of account types, and the differences change how an invitation should be sent.

A meeting organized from a personal Google Account, Google One, or Workspace Individual can be joined by all Google Account users. Anyone who has not signed in to a Google Account has to request to join, which means somebody already in the call has to be watching for the request. A meeting organized on a Workspace account can, by default, be joined by all Google Account users and by people who have not signed in at all, and an administrator can narrow that to signed-in users only, or to the organization only. On Workspace for Education the default is the opposite way round: only users in the school, plus anyone dialling in by phone, unless an administrator opens it up.

Forwarding is allowed but not equivalent to inviting. Google states that guests can forward the meeting link to other people, and that if an uninvited person tries to join, a participant from the organization has to accept the request before they get in. For a call where the first two minutes matter, that is a hold at the door rather than an open path.

There is a second asymmetry worth knowing before a call with an outside company. Google documents that administrators on the other side can restrict which meetings their own users are allowed to join, including meetings organized by personal accounts. A guest who cannot join a link that works for everybody else is usually hitting that rule, and the fix is on their side, not yours.

The practical consequence is simple. Add every attendee to the guest list on the event, including the ones who will be forwarded the details anyway, so nobody arrives at a waiting room that needs a human to open.

The limits that decide whether the meeting finishes

Numbers matter here because they end calls mid sentence.

On a personal Google Account at no cost, Google states that anyone can invite up to 100 participants and meet for up to 60 minutes per meeting. The detail that catches people out is in Google's help: meetings with three or more participants are limited to 60 minutes, and at 50 minutes everyone receives a chime and a message that the meeting is about to end. One to one calls and mobile calls have no time limit.

On paid Workspace plans, Google's own comparison lists 100 participants on Starter, 150 on Standard, 500 on Plus and 1000 on Enterprise, with a maximum meeting length of 24 hours across the paid tiers.

One restriction is easy to miss when a colleague's instructions do not match what you see. Google states that Google Workspace Essentials users cannot schedule a meeting in Google Calendar. The conferencing field is simply not available, and no setting changes it.

Scheduling from a Mac calendar instead of a browser tab

Plenty of this work happens in a desktop calendar rather than at calendar.google.com, and Google publishes a warning that directly affects how such an app should be built. If Google Calendar events with Google Meet codes are created in Apple Calendar or other calendar applications, a new meeting code might be generated automatically to protect the privacy and security of the meeting, and an email notification is sent when that happens. Google's recommendation is to manage meeting links from the Google Calendar apps or from calendar.google.com.

The distinction underneath that warning is worth understanding before choosing any Mac calendar. An application can either ask Google to create the conference on the event, which is what the web interface does, or it can write a link into the event's text, which is what the multiple conferences problem is made of. Only the first approach keeps the code tied to the event, keeps the guest list as the access list, and keeps the 60 day Calendar expiry rule rather than the 365 day one.

So the question to ask about a desktop calendar is not whether it shows Meet links. It is whether it creates them through Google. That, along with which accounts an app can sign into, is what the comparison page sets out, and the mechanics of getting an event and its guests entered quickly are covered in entering events. Travel time is the other half of the same problem, since a video call needs no journey but the meeting before it might, which is handled under travel time.

What to change first

Create the meeting from the calendar event rather than from the Meet homepage whenever it has a time and a guest list, and never paste a link into the description alongside it. If most of that work happens on a Mac, use a calendar that creates the conference through Google rather than writing a link into the event, which is what Caltimate does.