“When is the workshop?” asks for information. “Move the workshop to Friday” asks for a change. Once an AI assistant has app connections, those two sentences can produce very different results beyond the chat window.
Google describes Gemini connections that can retrieve information and, with permission, take actions. The details depend on the app, account, device and availability. A connected app label alone does not tell you every operation it supports.
Check the connection’s actual capabilities
In Gemini’s Connected Apps settings, open the app’s details and read its supported and unsupported actions. The general help page covers personal accounts; organisations can have different arrangements.
For Google Calendar, the current instructions include finding, creating and editing events through the Google Workspace connection. They also list limits: Gemini cannot add or invite people to events, or update an existing event’s location or description. Do not assume that a fluent request makes an unsupported operation available.
Ask for a proposal before a change
For an unfamiliar workflow, start narrowly: ask for a proposed event in the chat and explicitly say not to create or change anything yet. Inspect the date, time zone, duration and destination calendar. This wording communicates your intention; it does not replace actual permission controls.
Suppose a workshop email says “Friday at six”. That leaves a date and a morning-or-evening ambiguity, perhaps a time zone too. Resolve those details before asking the assistant to add anything. Google notes that Gemini uses the default calendar unless you specify another one.
Review any confirmation the product presents. If the workflow does not offer the control you need, make the change directly in the calendar app instead of relying on a promised extra confirmation step.
Verify where the change belongs
Open the event in the calendar itself. Check the account, date, time and duplicates rather than treating “done” in the chat as sufficient proof. If a response is unclear, inspect the calendar before repeating the creation request.
Be particularly careful with existing shared events. Google notes that some effects, such as an email already sent to guests after an edit, cannot be undone. Correcting a calendar entry afterwards does not necessarily recall every consequence.