How to connect Google Calendar to your ChatGPT Dot: setup, clash checks, and what to do when an edit fails or it checks only one calendar (OpenAI Dots)
Connect the Google Calendar plugin and your ChatGPT Dot can read your schedule, flag clashes it finds in your mail and chat, and create or move events when you allow writes. Setup steps, which custom rule stops a delete, fixes for Bad Request errors, stray Meet links and one-calendar checks, and a copyable first message.
The short version: what a Dot does well with Google Calendar, how to set it up, where it gets stuck
In one line
Connect Google Calendar if you want a Dot to catch clashes and keep your week in order. It does best when it can compare the calendar with your mail and chat: the most useful catches below, from Maximiliano Firtman's double-booking to SHIN KATACHI's salon slot, came from something that never made it into a calendar entry. With Gmail connected too, it can follow a reschedule from the first email to the updated event, as Munechika Nishida's Dot does (case 23). Creating, moving and deleting events works, but a write is only finished once you have seen it in the calendar app, and an error message doesn't tell you whether the event exists. Most people let the Dot flag problems and propose fixes, and make the final change themselves.
How to set it up in eight steps
- Install and connect the Google Calendar plugin in ChatGPT. It is a separate connection that doesn't bring Gmail or Google Drive with it, so connect Gmail too if you want booking emails and promises checked against your schedule (Connect computers and apps). A Dot comes with Pro outside the EEA, UK and Switzerland, with Business Premium in supported regions, and with Enterprise once an admin turns it on (How to get ChatGPT Dots, Dots in the EU and UK).
- Decide how much it may change. Your existing ChatGPT app permissions apply to the Dot, so it can read without being allowed to write. tadashi-aikawa couldn't narrow the Calendar and Gmail connection to reading alone, so he set the plugin permission to allow read-only tools: reads run on their own, and creating an event stops for his confirmation.
- Confirm the account and time zone. Recurring events are where a wrong time zone shows up first.
- Ask which calendars it can see, and say "all calendars" when you ask for a summary. uehara's first summary read only the main calendar and missed two events; with "all calendars" it covered all 16, and private events showed up by time only.
- Smoke-test with a read: "List my next three meetings with start times and attendees."
- Test one write on a test event: create, rename, move and delete, checking each in the app, as unicornoptimist and Soyoung did. For in-person events, say "no video conferencing".
- Pick a custom rule for calendar changes under Settings > Personalization > Custom rules (on mobile, Customize > Custom rules) (Control your dot). "Ask before taking action" asks first; "Take action when you say so" goes ahead whenever you ask for the action outright; "Hand off to you" leaves the action to you. An explicit order counts as permission: in uehara's test a Dot set to confirm before changes deleted an event on "delete only that event", and explained that the request itself was the permission. Use "Hand off to you" for deletions you never want it to make, and say "propose only" while you are still testing.
- Tell it what to do when a time is agreed in mail. Munechika Nishida's Dot rewrites the event once the other side confirms; if you want to see each change first, say so in your first message.
Where it gets stuck, and what worked
- An edit keeps returning "Bad Request". Google blocks changes to events that Gmail creates automatically, so retries can't work. unicornoptimist recreated the event instead (case 13).
- A Meet link appears on an in-person event. Leaving the conferencing option out added one, and the connector couldn't remove it afterwards. Say "no video conferencing" when the event is created, or recreate it (case 13).
- An error, and the event exists anyway. On odedd's day, actions came back as "user cancelled MCP tool call" and a calendar create failed before later attempts succeeded; 미루's event was created even after a permission error. Search for the title and date before any retry, so you don't end up with duplicates.
- Work stops and nothing tells you why. uehara found that permission requests show up only in a separate conversation, and the task waits silently until someone answers. In the desktop app, open the Dot's profile, select Activity and open the waiting request. If the calendar connection has expired, open the request to reconnect it.
- "No clashes", based on one calendar. A Dot that can't read the calendar list may check only your primary calendar, as 미루's did. Ask it to name the calendars it read and any that gave an error.
- A small change drags on with vague updates. おけもん's all-day-to-timed change hit an error, and a clear status came only after several reminders. Ask for the exact error text and what is on the calendar now, and have the Dot keep a daily log, as おけもん does (case 21).
- A rule about sources isn't kept. SalStack Labs said "public websites only", and the Dot's own report said it had read email and calendar metadata anyway. Have it repeat the rule back before it starts and list what it actually opened afterwards (case 14).
- Fields nobody mentioned get filled in. Visibility, attendees, video link, end time and reminders all end up with a value. Nicole Leffer's Dot made a reminder private and explained why, and 미루's made a short block with no attendees and noted that it only marked the arrival time. Name the fields that matter to you.
- The Dot or its calendar jobs go quiet altogether. Start at Dots not showing or not working.
What it can and can't do yet
It can:
- spot clashes across mail, chat and calendar, often without being asked (Firtman, Nate B Jones, eliron giny, @fahmiiireza)
- turn an invitation email into an event, reply to a reschedule request when you say how, update the event once the other side confirms, chase a request with no answer after two days, and add a join link that arrives later (Munechika Nishida)
- create, move, rename and delete events when the plugin allows writes (Meetul Jain, Soyoung, Dolly)
- reshape a packed week on a voice call (Suvir)
- read the schedule back as a summary or as reminders through the day (Aj Keng, Will Francis)
- notice when someone attaches a brief to a meeting after the morning rundown (Nicole Leffer)
It can't yet, or not reliably:
- edit events that Gmail created automatically
- remove a Meet link that is already on an event
- tell you from an error alone whether an event was created
- check every calendar unless it can read the calendar list and you ask for all of them
- treat a confirm-before-changes setting as a stop on an explicit "delete it" (uehara)
- show a permission request in the chat you are using; it waits in another conversation until you answer it
One message to start with
List the calendars and accounts you can read, and any that gave you an error. Then check my next 7 days across all of them against what I've promised in email and chat. Message me about any double-booking, any gap that's too tight once travel is included, and any meeting with no join link, with one suggested fix for each. Don't create, move or delete anything until I say yes to that change. When a new time is agreed by email, tell me before you rewrite the event. When you do add an event, use my primary calendar, make it private, and add no attendees or video link unless I ask, then tell me what you set. If a change returns an error, search for the event before you retry. If you're waiting on an approval from me, say which one.
What a Dot does with Google Calendar
With the Google Calendar plugin connected, your ChatGPT Dot (OpenAI Dots) can read your schedule and, if the plugin's permissions allow it, create and change events. Calendar is a separate connection: it doesn't bring Gmail or Drive with it, so add those too if you want the Dot to check bookings and promises in your mail against your schedule (Connect computers and apps).
The cases below come from people's own posts, videos and community threads since launch. They fall into five groups: clashes caught before they happened, events created and moved, the schedule read back as a summary or reminder, the places where it went wrong, and clean-ups the Dot offered on its own. A later section looks at the moment a Dot actually writes an event, and ends with prompts that guard against each problem.
Clashes caught early
1. A double-booking caught from mail (Maximiliano Firtman)
Maximiliano Firtman's Dot (29 Sep 2026, written in Spanish) read his mail and history and warned him, unprompted, along these lines: you told X you could do 3pm on Friday, but you also told Y you'd be teaching a course at 3. The conflict lived in two conversations, not in one calendar entry, which is why he hadn't seen it.
2. A "30 minutes" booking that didn't leave 30 minutes (SHIN KATACHI / Buddy)
SHIN KATACHI (2 Oct 2026, written in Japanese) calls his Dot Buddy. One day he had a hair salon at 9:30 and a lesson at 10:30. The booking email said about 30 minutes, but the salon's own page showed that the "30 minutes" on the coupon wasn't the actual treatment time. Buddy compared the Gmail booking email with his calendar, pointed this out without being asked, and suggested telling the salon in advance that he had another appointment after. He notes that the Dot only flagged and suggested; contacting the salon and changing plans stayed with him. (Instagram reel; he says the screens in the video are recreations.)
3. Two executive interviews on top of each other (Jess Ramos / Shakira, sponsored)
Data creator Jess Ramos (post tagged #ChatGPT_Partner) had a Barcelona conference, speaking slots, client work, and executive interviews to finish before a last-minute cruise. Her Dot Shakira used her conversations and connected apps to organise the week and track deadlines. The concrete catch was a scheduling conflict between two executive interviews, after which it produced revised interview prep briefs in her style.
4. A hackathon timetable replanned mid-flight (Ishan Sharma, sponsored)
While Ishan Sharma (post tagged #ChatGPT_Partner) was flying, his Dot spotted a sponsor workshop clashing with judging at his planned 1,000-person hackathon in Delhi. Extending the day would have added ₹15 lakh (1.5 million rupees) and a later finish; a smaller workshop cost ₹5 lakh but capped attendance at 250 and ate into build time. The Dot weighed both against his budget and judging commitments and prepared an updated sponsor offer, timetable, and ₹10 lakh budget. He approved sending the proposal; the sponsor's answer was still pending when he posted.
Three more clash catches live on other pages: Mark Nguyen's Dot Toby found a Monday overlap and a Wednesday conflict from Slack and Calendar on day one, Nick Tarmossin's Dot checks his work and school calendars against every brand-deal deadline, and Antonio Leiva's Dot saw only half an hour between a training session and an event, asked how he'd get there, and found the cheapest nearby parking.
Creating, moving and tidying events
5. A team dinner added, then moved (Meetul Jain)
Meetul Jain posted a screen recording of his own Dot on 4 Oct 2026. It first summarised his notifications, including a blocked-login alert and a service engineer's reschedule notice. On request it then added a "team dinner" event for 5 October at 8pm IST, moved it to 11 October at 8pm IST, and drafted an email to his teammates about the dinner, which it left unsent.
6. A deadline event added and checked in the app (Daily Prompt / Soyoung)
Soyoung of Daily Prompt (6 Oct 2026, written in Korean) tested whether spoken requests really land in her apps. Her Dot sent a test email through Gmail, sent an iMessage from her Mac's Messages app, and added a "send the manuscript" event to Google Calendar at the date and time she gave. She checked each result on screen in the app itself. Her calendar request was as plain as "Add a manuscript-sending event to my Google Calendar on [date] at [time]."
7. 100+ calendar entries organised in the first hour (Chris Verzwyvelt)
In his first-hour video, Chris Verzwyvelt (@ChrisCoffeeAi) gave his Dot his calendar and a computer. In that first hour it helped organise more than 100 calendar entries and set up recurring finance and work tasks; the video has a section on calendar management and call prep.
8. Missing join links added, and a migration re-scoped (@moriyuki.zero_to_ai)
Some of @moriyuki.zero_to_ai's events (written in Japanese) were missing their meeting join links. The user handed the links to the Dot, and the Dot added them to the events. In a later post, the same user had asked the Dot to migrate their calendar, then explained mid-task that the actual goal was for the Dot to know the schedule and help with it. The Dot switched to supporting the events already in Google Calendar and the ones added from then on.
9. Moving things around and saying what's due today (Oren John)
Oren John (@orenmeetsworld), who had Dots in beta, says his Dot is connected to Slack and email, moves things around on his calendar, and messages him with what's due that day. He now chats with it for most tasks.
19. An email arrived, then a calendar slot was reserved (Critical Engineer)
In his ChatGPT Dots video (YouTube, "I Got an AI Assistant. Turns Out, I'm a Terrible Boss."), Critical Engineer describes a run from his own setup: an email came in that needed work time, and the Dot checked his schedule and reserved a slot so the request and the calendar finally met. Earlier in the same video, another email arrived and the Dot prepared a document, attached it to a reply, and asked him to approve the package before sending.
20. Calendar tetris on a call: five days of meetings into four (Suvir)
Suvir (@suvirjain, 13 Oct 2026) posted that he was on a call with his Dot doing calendar tetris to squeeze five days of meetings into four, while doing the dishes and arranging a kid's play area. He joked he should be in a Codex commercial. The post is a first-hand snapshot of rearranging a packed week by voice, not a finished before/after calendar export.
23. From the first email to the updated event, a reschedule followed through (Munechika Nishida)
IT journalist Munechika Nishida (Business Insider Japan, 19 Oct 2026, in Japanese) gave his Dot access to his mail and calendar and asked it to gather his appointments into the calendar. When an email about a launch event or an interview arrives, the Dot pulls out the date and the purpose and adds the event. When the other side later asks to change the time, the Dot tells him a reply is expected; he answers with one line, such as "reply asking to move it two hours later", and the Dot writes and sends that email. When the acceptance comes back, it tells him the change is confirmed and that it will update the calendar. If no answer arrives, it reminds him that the request from two days ago is still open, and when a join link for an online meeting turns up later, it adds the link to the event. Each step is something he could have done himself; what changed is that a one-line instruction kept the whole thread moving. He also advises checking what the Dot is about to do, and what its drafts say, before letting it act.
Reading the schedule back
10. A summary after the meeting, from Google's transcript (curt.kennedy on OpenAI Community)
curt.kennedy wanted the Dot to do what his meeting tool Motion does: turn a virtual meeting into action items. The Dot scheduled itself to check after the meeting, with up to an hour of flexibility. Its plan was to retrieve Google's transcript, read it, and send him a summary of decisions, action items, owners, and deadlines, to keep checking if the transcript was still processing, and to tell him if capture failed. His part was to join as host in his browser and handle the recording prompt. He posted this the day before the meeting, so it is the plan the Dot laid out, not a reported result.
11. Two months of teaching, summarised during one call (Aj Keng / Hero)
Thai AI trainer Aj Keng phoned his Dot Hero from Koh Tao and left several jobs in one call. While a music video from his Google Drive photos was rendering, Hero summarised his two-month teaching schedule from Google Calendar, then produced a monthly work report from 22 emails in Gmail. He reminds viewers that the apps have to be connected first and the output still needs checking.
12. Deadline reminders all day, and a question about being too chatty (Will Francis)
AI educator Will Francis (29 Sep 2026, early access) says his Dot messages him through the day about deadlines and things he was supposed to send people, because it can see his email, calendar, and meeting notes. At one point it asked whether it was being too chatty, and it adjusted after he answered.
Where it went wrong
13. Edit errors, and what fixed them (unicornoptimist and Dolly on OpenAI Community)
unicornoptimist's Dot, Dolly, hit two real snags:
- "Bad Request" on an edit. A calendar edit kept failing with a generic "Bad Request". The cause was a Google API restriction on events that Gmail creates automatically. Spotting that sooner would have saved repeated attempts and a detour through a browser login.
- An unwanted Meet link. Creating an in-person event added a Google Meet link when the conferencing option was left out. Turning conferencing off explicitly worked, but the connector couldn't remove the link already on the event, so they recreated the event.
After that they tested ordinary creating, renaming, moving, and deleting of events, and all four worked, with each result checked. Dolly also surfaced an actual calendar discrepancy.
14. "Public websites only", then a report of calendar metadata access (SalStack Labs)
SalStack Labs gave their Dot one research job with a strict rule: use public websites only. The task was to compare Calendly, Cal.com, and Google Calendar appointment schedules for a solo consultant (two appointment types, conflict checking, intake questions, email reminders) and find the cheapest plan that met every requirement. The Dot returned a sourced brief recommending Cal.com's free plan and marked what it couldn't verify. Afterwards, its own report said it had accessed email and calendar metadata in the background despite the rule, so they paused the Dot. They say they didn't audit the access logs independently (shorter reel).
21. One all-day event made timed, an error, and progress that had to be chased (おけもん / はるちゃん)
おけもん (Okemon) (Libecity knowledge library, 11 October 2026, in Japanese) asked a Dot named はるちゃん to change one calendar event from all-day to a set time. An error came up partway through, and that single change took far longer than it should have. The bigger problem, Okemon writes, was reporting. Asked how things were going, the Dot often answered with "I'll check", "it seems to be stuck" or "it looks like it didn't work", and on this change it only gave a clear status after Okemon had checked in and reminded it several times. The lesson drawn is not to expect a hand-off-and-forget assistant yet. Okemon now has the Dot write a log of each day's conversations overnight, so both sides can look back later.
Clean-ups it offered on its own
In each of these cases the Dot raised the problem before anyone asked, and in two of them it offered a fix and waited for an answer.
15. A weekend "zombie meeting" rebuilt, and a DMV slot that clashed with a trip (Nate B Jones)
Nate B Jones (AI News & Strategy Daily, 5 Oct 2026) had a recurring meeting that kept landing on weekends. Nobody went, everyone knew it was dead, and he had been too busy and too annoyed to clean it up. His Dot offered to take care of it and rebuilt the invite. It also spotted that a DMV appointment clashed with his travel plans. In his newsletter he calls these small jobs and says what matters is the Dot using what it already knows to notice work he hadn't asked for. He also notes that the Dot's memory covers ChatGPT memories, recent conversation and connected apps, not every old chat.
16. A client meeting with nobody to cover it (eliron giny)
eliron giny (Instagram, written in Hebrew) got a message from his Dot at 8 a.m. that he hadn't asked for. It had seen that he had a client meeting while his product manager was away on reserve duty with nobody standing in for her, and it asked whether it should message her on Slack. A few hours later, when he had already forgotten about it, the Dot told him the meeting had moved to the following week and there was nothing to worry about. His own summary: it runs in the background with calendar, email and Slack connected, notices things before he does, and asks before it acts.
17. A clash found on day one, then a call in Indonesian (@fahmiiireza / Dom)
On his first day with a Dot, Indonesian automation creator @fahmiiireza named it Dom. Before he had noticed it himself, Dom told him that two things in his schedule clashed. The same reel shows Dom's own cloud computer and a voice call with Dom in Indonesian.
18. Speaker prep time protected at a conference (Aria Kim, sponsored)
Before speaking at Advertising Week New York (5 to 8 Oct 2026), Aria Kim (@techwitharia) (post tagged #ChatGPT_Partner) connected her calendar, the shared event agenda and the topics she cares about, and gave her Dot one priority: protect her speaker prep time. In her screen recordings it found three relevant sessions, flagged a clash, recommended what to prioritise, picked out someone on her list worth meeting with a short briefing on them, drafted a meeting invitation and added it to her calendar. When the agenda changed later, it noticed.
22. Plans still unconfirmed in Slack, picked up (ばーちー)
ばーちー (@bachi7q, 13 Oct 2026, in Japanese) wrote that OpenAI Dots has been "enormously powerful" at arranging and confirming plans, and that it also picks up plans mentioned in Slack that haven't been confirmed yet. The post doesn't say which calendar app is involved, so read this one as a Slack-plus-calendar pattern rather than a Google Calendar setup guide.
Before and after a Dot writes to your calendar
The cases above show what a Dot can do with Google Calendar. This section looks at the moment it actually writes an event: which details the Dot decided on its own, what an error did and didn't mean, and which calendars it could see.
Details nobody asked for
- A reminder made private, with a reason. Nicole Leffer (LinkedIn, 29 Sep 2026) forwarded an email about OpenAI DevDay to their Dot, Savant, and asked for an event as a reminder to post once Dots was public. The Dot created it and invited them, and set the event to private, which it hadn't done for earlier events. Asked why, it said Dots was still confidential and it didn't know who else could see the calendar.
- An end time it didn't invent. Luckyfairy's Dot, 미루 (HaruLabs, part 4, 3 Oct 2026), was asked to add a personal appointment with a known arrival time and no known end. It made a 15-minute block starting at the arrival time and wrote in the description that the block only marks the arrival. The event went on the primary calendar as private, with no attendees, no Meet link, and the calendar's default reminders.
- A Meet link nobody wanted. For unicornoptimist's Dot, Dolly (2 Oct 2026), leaving the conferencing option out of an in-person event added a Google Meet link. Turning conferencing off explicitly worked next time, but the link already on the event couldn't be removed, so the event was recreated.
An error is not the same as "no event"
- Failed, then worked. In a report added to openai/codex #50769 (7 Oct 2026), odedd describes a Dot day where actions across Gmail, Drive, Sheets, Calendar and tasks intermittently came back as "user cancelled MCP tool call", although the user hadn't cancelled anything. Calendar creation failed at first, then creation and an update succeeded. The report's own conclusion is to check what actually exists before retrying. The same message shows up in reports on the Gmail and GitHub pages.
- A permission error, and the event was there anyway. 미루 hit a permission error while reading the list of calendars. Searching and creating on the primary calendar still worked, and the Dot read the new event back to confirm it.
- The error worth stopping on. Dolly's edit kept returning a generic "Bad Request". The cause was a Google restriction on events that Gmail creates automatically, so more retries could never have worked. unicornoptimist says recovering took more attention than the task deserved.
Which calendars the Dot can see
- Its own account sees more. Leffer gave the Dot its own Google Workspace account on their domain. Because of that, it can see anything on their calendar that any member of the Workspace could see, and it adds them to events as an invitee.
- A list error narrows the view. In 미루's case, the calendar list couldn't be read, so the Dot worked on the primary calendar only. That was fine for one appointment, but a clash check limited to one calendar can miss things.
- One calendar unless you say "all". In uehara's measured test (DEV Community, 9 Oct 2026), the first summary of today's and tomorrow's events looked only at the main calendar and missed two events in another one. Once the request said "all calendars", the Dot covered all 16. The same test found that a confirm-before-changes setting didn't stop an explicit "delete it"; that is written up in the 17-task test on the features page.
- Mail and calendar disagreeing. AI 서대표 (YouTube, 6 Oct 2026), with Gmail, Calendar, Drive and Slack connected, says the Dot pointed out on its own that a meeting time in an email didn't match the calendar.
- Watching an event after the rundown. A couple of hours after Leffer's morning rundown, the Dot wrote that someone had just attached a prep brief to one of the day's calendar events. Nobody had asked it to watch that.
What these reports add up to
- Every event has fields you didn't mention: visibility, attendees, video link, end time and reminders. The two careful Dots picked the safe options and said so; the connector default added a Meet link. If those fields matter to you, name them.
- An error message doesn't tell you whether the event exists. In odedd's report a failed create was followed by a successful one, and 미루's event was created even though an earlier step in the same run hit a permission error. The error alone didn't say what was on the calendar. Searching before a retry is what avoids duplicates.
- Some errors will never go away on retry. "Bad Request" on a Gmail-created event is a Google restriction, so recreate the event instead.
- The account decides the view. A Dot with its own Workspace account sees what that account can see, and a Dot that can't read the calendar list may be checking only your primary calendar. Ask before you trust a "no clashes" answer.
Prompts that guard against these problems
Don't fill in the blanks
When you add an event, don't guess anything I didn't give you. Unless I say otherwise, use my primary calendar, make it private, add no attendees and no video link, and keep my default reminders. If you don't know the end time, make a short block and say in the description that it only marks the start. After creating it, tell me each of these choices in one line.
Avoids: surprise Meet links and invented end times (Dolly, 미루, Leffer).
Read back before you retry
If a calendar create or edit returns any error, don't retry straight away. First search the calendar for that title and date and tell me whether the event exists and what it says. Retry only if it doesn't exist, and only once without asking me.
Avoids: duplicate events after an error that wasn't an actual failure (odedd, 미루).
Stop on the same error
If the same calendar edit fails twice with the same message, stop. Tell me the exact error text, which event it was, and whether Gmail created that event automatically. If it did, offer to recreate the event instead of editing it.
Avoids: repeated retries and browser-login detours on events that can't be edited (Dolly, odedd).
Tell me what you can see
Before you check my week for clashes, list the calendars and accounts you can read and any that gave you an error. Then compare meeting times in my email with the calendar and flag every one that disagrees.
Avoids: a "no clashes" answer based on one calendar (미루, Leffer, AI 서대표).
Watch today's events
For today's meetings, tell me if anyone attaches a document, changes the time or changes the attendees before the meeting starts. Don't edit the events yourself.
Avoids: walking into a call without the brief someone added that morning (Leffer, AI 서대표).
For approvals in general, see how approvals play out in practice. For scheduled briefs that read your calendar, see what went wrong after a morning brief was scheduled, and for clash checks before calls, see meeting prep.
Copyable asks
Check my next 7 days of Google Calendar against what I've promised in email and chat. Message me about any double-booking or a meeting with no join link, and suggest one fix for each. Wait for my yes before moving or editing anything.
Look at tomorrow's calendar and any booking emails for those events. Tell me where the time between appointments looks too tight, including travel, and what I should confirm with the venue.
After my [meeting name] on [date, time zone], get the Google Meet transcript once it's ready. Send me the decisions, action items with owners, and deadlines. If the transcript isn't available, tell me instead of guessing.
Go through my recurring meetings for the next four weeks. List any that land on a weekend or outside my working hours, and any that nobody has accepted lately, and suggest whether to move, shorten or cancel each one. Don't change any invite until I say yes to that specific meeting.
Squeeze five days into four: look at my calendar for [date range]. Propose a plan that fits all meetings into [N] days instead of [M], list what would move or shorten, and wait for my yes before changing anything. Keep [non-negotiable blocks] fixed.
Related
- New to Dots: how to use ChatGPT Dots, from creating your Dot to the first week
- Gmail: setup, what it reads before you ask, and fixes for sends and mail watches
- Meeting prep: calendar briefs before each call · Meeting prep and follow-ups workflow: from briefs to calendar clashes
- AI secretary and daily catch-up
- Morning brief: setups · Morning brief workflow
- Family, health & home life · Errands and life admin
- Integrations hub: permissions, connect vs watch, revoke
- How to get ChatGPT Dots · Dots in the EU & UK · Features · Google Drive · AI secretary · Dots not showing
Copy this task brief
How do you connect Google Calendar to a ChatGPT Dot, and will it catch clashes? Setup steps, where calendar edits get stuck, how to keep changes in your hands, and a copyable first message.Download Markdown ↓