Define the meeting before searching the calendar
Suppose two colleagues need a 25-minute equipment-handover call next week. One works in New York and the other in Los Angeles. Their names alone do not identify which email addresses should receive an invitation.
Supply the actual date range, both addresses and the working-hour constraints. Avoid “tomorrow afternoon” when the participants use different time zones.
Use my connected Google Calendar to propose a 25-minute handover.
Date range: [EXACT START DATE] through [EXACT END DATE].
Organizer calendar: [CALENDAR NAME / ACCOUNT].
Required attendees: [VERIFIED EMAIL A], [VERIFIED EMAIL B].
Use each attendee's stated working hours: [HOURS AND TIME ZONES].
Find up to three mutually available slots. Show each date and
time in America/New_York and America/Los_Angeles. State which
calendars or availability information you could actually check.
If you cannot check someone's availability, mark it unknown.
Do not create or change an event, send an invitation, or respond
to any existing invitation yet.
This authored prompt asks for evidence before an action. If a colleague's calendar is inaccessible, an empty search result does not establish that they are free. Ask them to confirm the proposed time through your normal scheduling process.
Connect the intended calendar account
Use Claude's Google Calendar connector and authenticate the relevant Google account. Team and Enterprise organizations require an Owner or Primary Owner to enable connectors before members connect individually. You can toggle individual connectors from + > Connectors. Connection and permission conditions
Check the organizer calendar in the response. A personal calendar and a shared operations calendar can both be accessible but produce different ownership and visibility. Specify which should hold the event instead of accepting the first calendar Claude finds.
Review one proposed event before creating it
Choose a slot and request a final event proposal containing its title, date, start, end, time zones, organizer calendar, attendee addresses, location or call details, and recurrence. For a one-time handover, recurrence should be off.
Read the addresses character by character. A similar display name can refer to a different colleague. Check the actual dated times in both zones; do not apply a remembered offset to every week of the year.
Then authorize only that event. By default Claude requests explicit approval for actions; managed organizations can configure some actions to run without asking each time. Your own “propose first” instruction makes the desired boundary clear, but you should still inspect the actual action offered. Action approval behavior
Confirm the event in Google Calendar
Open the created event in Google Calendar and check its calendar, full date, 25-minute duration and attendee list. If the creation response is unclear, look for an existing event before retrying so you do not create a duplicate.
An invitation and an accepted invitation are different states. Keep an attendee's response unconfirmed until the calendar or the person confirms it.
For a separate message to accompany the invite, Claude's Gmail workflow covers checking the thread and recipient before sending. Finish this task with one verified event and a clear record of whose availability or attendance is still unknown.