# How to connect Gmail, Slack, Drive or GitHub to your ChatGPT Dot: permission levels, a first test and fixes for five common failures

Connect Gmail, Calendar, Slack, Drive, Notion, GitHub or Teams to a ChatGPT Dot: pick the job first, set each app's permission level (Always ask, Allow read actions, Allow low-risk actions or Allow all actions), put sends behind Ask before taking action, then run a one-minute write test. Plus fixes for a false "user cancelled", approvals that miss the write, watches that go quiet and the wrong account.

How to connect apps to a ChatGPT Dot in seven steps, which permission level to pick for each app, a one-minute write test, fixes for the common blockers and one message you can copy.

These come from the failure reports on the six app guides (Gmail, Google Calendar, Slack, Google Drive, GitHub and Teams), grouped by what went wrong instead of by app. Each one links to the guide where the reports are told in full. The fixes are in the short version above.

### 1. "User cancelled" when you cancelled nothing

The message "user cancelled MCP tool call" turned up in Gmail sends and replies, in Google Calendar event creation, in an Outlook cleanup and in GitHub uploads (odedd and cedar_circuit on [Gmail](/integrations/gmail/), odedd again on [Google Calendar](/integrations/google-calendar/), tndd on [GitHub](/integrations/github/)). In none of these reports did the message say whether the action had actually happened. Some sends never went out, one calendar create worked on the next try, and one GitHub upload that looked lost turned up hours later (konard). More reports with the same wording, in Slack, a private mail server, a spreadsheet, JobTread and the Dot's own task creation, are collected under [Dots not working](/dots-not-showing/), section 12.

### 2. A yes that doesn't reach the exact action

Approvals are matched against the specific write. On [GitHub](/integrations/github/), a general go-ahead didn't cover a later batch of files, a new branch or a comment (jabdori, seeton, carabinshely), a saved merge rule didn't cover the merge (DmitrL-dev), and a yes relayed from the main Dot conversation into a delegated task was treated as untrusted (Beowulfwar, misosiruda). On [Gmail](/integrations/gmail/), a sign-in code the Dot found in the inbox was refused because it had to come from the user (ammpanda). What unblocked one GitHub case was a single question that named the files, the repository and the draft PR together.

### 3. Reading works, so the connection looks fine, but writing or watching doesn't

In almost every failure report the read side kept working. A Gmail watch stopped waking the Dot while an on-demand search still found the email (anotb, Daareek on [Gmail](/integrations/gmail/)). A Dot in Slack read channels but couldn't reply, with error -32603 ([Slack](/integrations/slack/)). Drive search and metadata kept working while a 514 MB upload and a 52 MB download never arrived (COOLak, sbosell on [Google Drive](/integrations/google-drive/)). A successful lookup tells you little about a send, an upload or a trigger.

### 4. Two routes into the same app

Several apps can be reached two ways, and the two fail separately. The Drive plugin uses the permissions you approved in ChatGPT, while a Google sign-in in the Dot's own browser is a separate login that Google challenged (COOLak on [Google Drive](/integrations/google-drive/)). The GitHub plugin kept working while gh CLI and git push in the Dot's cloud shell had no login (s520145, konard and f0909172434 on [GitHub](/integrations/github/)). In Slack, the Dot's dedicated sending route worked again while the general message route still returned -32603 (nittajun, markguoz on [Slack](/integrations/slack/)). Teams messaging and the Teams plugin are separate connections too ([Teams](/integrations/teams/)).

### 5. The wrong account, or a narrower view than you think

Adding a second Gmail account stopped a new-mail trigger, and the task editor had no way to choose which account it watched (Daareek). A Dot that couldn't read the calendar list worked from the primary calendar only, so its clash check covered one calendar (미루 on [Google Calendar](/integrations/google-calendar/)). A Dot with its own Workspace account could see whatever that account could see (Nicole Leffer). On [GitHub](/integrations/github/), an upstream repository missing from the app's repository list returned 403 (articultur), and a repository selection that never saved led to refusals (partialobserver). A hosted IMAP mailbox can't be connected at all (TheIgnacioLok on [Gmail](/integrations/gmail/)).

Source: https://gptdot.net/integrations/
