ChatGPT Connectors (2026): Which Apps Connect, What Each Plan Gets, and How to Set Them Up Safely

ChatGPT connectors: the short answer

As of September 2026, ChatGPT connectors are called apps, they ship inside plugins in the Plugin Directory, and they link ChatGPT to Google Drive (with Docs, Sheets, and Slides), Gmail, Google Calendar, SharePoint, Outlook Email and Calendar, Microsoft Teams, Slack, GitHub, Box, Dropbox, and more. Apps are enabled by default on ChatGPT Business ($20 a seat a month billed annually) and disabled by default on Enterprise; on personal plans you connect them yourself from Settings and Apps.

OpenAI rebuilt this whole area over the summer, so most "ChatGPT connectors" guides you'll find are describing a menu that no longer exists. On July 9, 2026 the App Directory became the Plugin Directory. An app is still the integration that reaches an outside service. A plugin is a package that can hold one or more apps, skills, and app templates. Installing a plugin doesn't skip the app's sign-in or your admin's permissions. The rename is the part that confuses people; the mechanics underneath are the same connectors you had.

Everything below comes from OpenAI's help center and pricing pages, read on September 15, 2026. Where OpenAI doesn't publish something, I say so.

Which apps connect to ChatGPT today

OpenAI doesn't publish one complete list; the directory lives inside the product and admins can export it as a CSV. These are the apps OpenAI's own pages name right now, and what each page says it does.

OpenAI's Business pricing page sums it up as "Connect to Google Workspace, Slack, GitHub, Microsoft 365, and more." If your tool isn't in the table, check the directory before assuming it isn't there; OpenAI adds plugins weekly and ranks them by whether people keep using them after install.

What each plan gets

OpenAI doesn't publish a per-plan connector grid. What it does publish, across the pricing page, the help center, and the release notes, adds up to this.

Two things worth flagging. The training default is the real line between personal plans and Business, not the connector list. And "individually authorized sync" is gone: if you want ChatGPT to pre-index a whole Drive or SharePoint so search is faster, a workspace admin has to set that up, which means Business or above. Personal plans get live access at chat time, which is fine for most owner-operators.

Admin controls: Business vs Enterprise

On Business, apps are on from day one. An owner or admin goes to Workspace settings, then Apps (or Admin, then Plugins), opens the Enabled tab, and for any app can review App details, set Action control, Disable it, or Manage domains so members can only connect accounts from your company's email domain. You can filter for every app with write actions and disable them as a group, which is what I do first on a new workspace.

On Enterprise and Edu, apps are off until an admin enables them, and the controls go deeper: role-based access per group, allow all actions or read-only or a custom set, a policy for how new actions are handled (enable all, read-only, or disabled until reviewed), parameter constraints on what arguments the model can send, and team-wide sync deployment. OpenAI's own line on the difference: "ChatGPT Business administrators manage whether an app is enabled for the workspace." Role-level control is not a Business feature.

One thing admins don't get on Business: your members' ordinary private conversations. The Compliance Platform, which exposes app-activity records, is Enterprise and Edu only. All app calls are logged there, not on Business.

Data access defaults you should know before connecting anything

• The default permission is "Important actions." ChatGPT reads from a connected app without asking, and asks before anything that could have a meaningful effect outside ChatGPT: sending an email, deleting content, making a purchase, uploading or moving a file, changing sharing settings, or sharing sensitive personal or financial information. The other options are Always ask, Allow read actions, Allow low-risk actions, and Allow all actions, which OpenAI says "carries elevated risk" and keeps out of the standard workspace-wide selector.
• Connectors inherit the account's permissions and nothing more. Connecting a personal Google account does not give ChatGPT your work Drive. Admin-managed sync doesn't grant members files they can't already open.
• Apps see context. An enabled app can receive relevant conversation context, Memory content if Memory is on, and website-style basics like IP address and approximate location. Data shared with an app follows that app's privacy policy, shown before you enable it.
• Google apps have a carve-out. Even with "Improve the model for everyone" on, OpenAI says it does not train on data accessed directly from connected Google apps, except conversations you submit as feedback, content you paste in yourself, or text that lands in ChatGPT's own response.
• Disconnecting isn't deleting. Disconnecting an app stops future access but does not remove existing chats, saved files, or memories. Deleted chats are scheduled for permanent deletion within 30 days.
• Voice mode doesn't support apps, and apps run on your plan's normal rate limits with no separate meter.

A 6-step setup for a small business

This assumes ChatGPT Business, because the no-training default and the domain restriction are the two things I won't skip for a company with client data. The Business plan setup itself is covered in my ChatGPT Business setup guide; this is the connector layer on top.

1. Set the workspace default permission before anyone connects anything. Workspace settings, General, Settings, Plugin permissions. I leave Important actions for most teams. If you handle money or health data, set Always ask and loosen it per app later.
2. Prune write actions. On the Enabled tab, filter for apps with write actions and disable the ones nobody needs on week one. Reading a Drive is low risk; letting ChatGPT send from Gmail is a policy decision, not a default.
3. Turn on Manage domains for every app you keep. Members should only be able to connect accounts at your company domain. This is the control that stops someone wiring their personal Gmail into a workspace that a client's contract says holds only company data.
4. Get your Google or Microsoft admin to approve the scopes. For Google, the Workspace admin trusts the ChatGPT/OpenAI OAuth app for the scopes behind the actions you left enabled. For Microsoft, an Entra administrator has to grant organization-wide consent through Configure Microsoft permissions in Admin, then Plugins. Approving the scope does not enable the action; you do both.
5. Have each person connect their own account. Open the Plugin Directory, pick the plugin, select Connect, and sign in with the work account. On Google's screen, choose Select all; OpenAI's page says the connection fails if any requested permission is left unchecked.
6. Test a read, then a write. "Find the latest proposal in Drive and summarize it" should just work. "Draft a reply to the last email from our accountant and send it" should stop at an approval card. If it doesn't, your permission level is wrong.

The three connectors to turn on first

Same answer as for Claude connectors: files, mail, calendar. Everything else can wait a month.

1. Google Drive or SharePoint. This is where the proposals, contracts, and price sheets live. One connection now covers Docs, Sheets, and Slides on the Google side. On Business, apps with sync can be deployed team-wide by an admin so search hits pre-indexed content instead of crawling at chat time.
2. Gmail or Outlook Email. Read-only first. The value is "what did the client say about the deadline" without tab-switching, not sending. Turn on send once the team has seen the approval card a few times and trusts it.
3. Google Calendar or Outlook Calendar. Cheap to connect, immediately useful for "what's on Thursday and what do I need to prep," and on the Google side it brings Meet transcripts and recordings with it.

Slack and GitHub are fourth and fifth if you use them; the webhook-triggered tasks that watch a Slack channel or a pull request are worth it, but only after the first three are boring.

What OpenAI doesn't publish

• A complete, public list of apps. The directory is in-product, and the CSV export is admin-only and up to 48 hours stale.
• A per-plan grid. Plan availability is described app by app in release notes.
• A date for the custom GPT retirement. OpenAI announced on September 11, 2026 that it plans to retire custom GPTs across plans with a migration to plugins, and says timing varies by plan and workspace. If your team built GPTs that lean on connectors, read Projects vs custom GPTs and start moving that logic into Projects or plugins now.

What this costs and who should buy which seat

For a company, connectors are a Business decision: $20 a seat a month billed annually for a Standard seat, $25 monthly, with Premium at $100 or $125 if someone burns through usage. The connector feature set is identical between the two seats; only usage differs. The full plan breakdown, including what Enterprise adds, is in ChatGPT Business pricing. For a solo owner with no client-data obligations, Plus at $20 gets the same apps without the admin layer, and the training setting is yours to turn off.