How to Connect ChatGPT or Claude to Your Business Apps

Connect ChatGPT through its apps (formerly called connectors) and Claude through its connectors: pick the app, sign in to the business account, and approve the permissions. For tools without a built-in option, add a custom MCP connection or route through Zapier or Make. Start read-only, on a business plan where an admin controls what's switched on.

Connecting takes a few clicks. Deciding what the AI may see and do is the real work. Once an app is connected, the assistant can usually reach whatever that account can reach: the whole inbox, every shared folder including old contracts and staff files, and, with write access switched on, the ability to send email or move documents. So the order below is permissions first, questions second. If you mainly want to know what ChatGPT can see once it's plugged into a drive or inbox, what ChatGPT connectors can see in your Drive and inbox goes deeper on exactly that.

Follow me on Instagram@sagnikteaches

Three ways in, and when each one fits

Almost every connection you'll make falls into one of three routes. Pick the simplest one that reaches the app you need.

Connect on LinkedInSagnik Bhattacharya

There's also a fourth route running the other way: the automation platform calls ChatGPT or Claude from inside a workflow, with no chat window involved. That suits jobs that should run on their own, such as classifying every new enquiry. Zapier vs Make vs n8n for AI automation covers that direction.

Subscribe on YouTube@codingliquids

What your plan allows, as of September 2026

Both vendors change these rules often, so treat this as a map to check against their help pages, not a promise.

For a team, a business plan is worth it for the admin controls alone. Both ChatGPT Business and Claude Team need at least two seats: $25 per seat a month on monthly billing, or $20 billed annually, on either one. A one-person business can connect apps on an individual plan, but loses the ability to lock down what's connected.

Connecting ChatGPT, step by step

1. Admin check (Business plans). Before anyone connects anything, review which apps are switched on in the workspace settings and turn off the ones your team shouldn't use yet. On Business, remember they start switched on.
2. Connect from a chat. Mention an app with @ or choose it from the + menu. If it needs your account, ChatGPT asks you to sign in; choose the account that already has access to the right information, and read the requested permissions before approving.
3. Manage and disconnect. At the time of writing, connected accounts sit under Settings, then Plugins, where you can review an app, add a second account, or disconnect. Disconnecting stops future access; it doesn't delete past chats or memories.
4. Ask a question you already know the answer to (the five test questions in the last section work well).

OpenAI's help article on apps in ChatGPT is the page to check for which apps your plan and workspace currently allow. On Business, company knowledge lets you ask one question across several connected tools and get an answer with citations back to each source, which is the fastest way to see what the AI can actually reach.

Here's how that plays out for an illustrative planner on ChatGPT Business with Slack and Google Drive connected. She selects company knowledge under the message box and asks: "What did we agree with the caterer about the vegan menu for the [client surname] wedding, and is it in the signed contract?" The illustrative answer comes back with two citations: "Slack, 4 September: the team agreed six vegan mains and a vegan dessert option. Drive, Caterer contract v2: lists four vegan mains and no dessert option." Useful, but it needed one fix before she acted on it. The Slack message was a colleague's summary of a phone call, not the caterer's own words, so the planner emailed the caterer to confirm before asking for a contract change. Citations tell you where an answer came from; they don't tell you whether that source was right.

Connecting Claude, step by step

1. Owner setup (Team and Enterprise). Enable the connectors you want in the organisation's settings page, under Connectors. Then set tool permissions: for Gmail, for instance, allow search and read, set sending to Needs approval, and block anything you don't need.
2. Connect from a chat. Click + in the chat box (or type /), hover over Connectors, choose Manage connectors, then click + beside Connectors to browse the directory. Pick the connector, review what it can read and write, and click Connect.
3. Microsoft 365 needs one more person. A Microsoft Entra Global Administrator has to authorise the integration for your organisation. Its write tools (sending email, creating files, posting in Teams) are off by default and need an administrator to switch them on.
4. Know the gaps. Claude's Gmail connector sees attachment details but not the attachment's contents, so a PDF quote in an email isn't read unless the file also sits in Drive.

The Claude help article on connectors lists the current steps and plan limits. If several people will ask the same kinds of questions, pair the connectors with a shared project holding your instructions; setting up Claude Projects as a shared team assistant shows how.

When the app you need isn't listed

Booking systems, niche CRMs and industry tools often have no built-in option. You have three ways round it.

• A custom MCP connection. If the vendor publishes a remote MCP server, add it as a custom connector in Claude, or as a custom app in ChatGPT once a Business admin has enabled developer mode (only admins and owners can publish custom apps to the workspace). OpenAI warns that untrusted MCP servers increase the risk of prompt injection, so only connect servers from vendors you already trust with the data.
• Zapier MCP. Zapier lets ChatGPT or Claude call actions in the apps Zapier supports. Each successful tool call uses two tasks from your Zapier plan, failed calls use none, and calls stop working when you reach the plan's task limit until it resets.
• Make's MCP server. Make can expose scenarios to ChatGPT or Claude as tools. In an MCP toolbox, the scenarios you've set to active with on-demand scheduling become the tools the assistant can run, with inputs it fills in and outputs it gets back.

The automation-platform routes have a hidden advantage: you decide exactly which actions exist. An assistant that can only call "add note to client record" can't delete the record, whatever an email tells it to do.

A wedding planner's setup, worked through

Take an illustrative two-person wedding planning business. It runs on Google Workspace (Gmail, Drive and Calendar), keeps client details in a small booking and CRM tool with no ChatGPT or Claude connector, and wants three things: summaries of long supplier email threads, answers from contracts in Drive, and quick availability checks.

They chose Claude Team at two seats on monthly billing, $50 a month, because the owner wanted per-tool approvals. The setup took about three hours over two days:

• Hour one: moved staff records, bank statements and anything else sensitive out of the shared Drive into a folder the connector's account can't open, and created a "Suppliers" folder holding only current contracts.
• Hour two: enabled Gmail, Drive and Calendar in the organisation's settings; set Gmail send, Drive trash and Calendar delete to Needs approval; blocked Drive sharing.
• Hour three: connected the booking tool through Zapier MCP with just two actions ("find client by name" and "add note to client"), on Zapier Professional at $29.99 a month. At two tasks per call, the 750 tasks cover 375 calls a month, far more than two planners need.

Total running cost: about $80 a month. Here is one of their first real prompts, with an illustrative answer.

Search my Gmail for messages from the florist since 1 August about the
[client surname] wedding on Saturday 12 June 2027. List every open question
or unconfirmed item with the date it was raised. Then check the florist's
contract in Drive (Suppliers / [client surname]) for the agreed delivery
time, and flag any conflict with the emails.

Illustrative answer: "Three open items. 1) Buttonhole count: the florist asked on 12 August whether it's 8 or 10; I found no reply. 2) Arch installation fee of $180, quoted on 20 August; no confirmation found. 3) Delivery time: the contract says 10:30am, but the florist's email of 3 September says 'around 11'. These conflict."

Two things needed fixing. The buttonhole question had been answered, from the planner's phone using a second email alias the connector's account didn't search. And the Drive folder held two versions of the contract; the AI read version 1 (10:30am) while version 3 said 11am, so the "conflict" wasn't real. The fixes were dull and permanent: add the alias to the account, and archive superseded contract versions in a separate folder. After that, the same prompt returned one genuine open item: the arch fee.

Permissions to set before anyone asks a real question

Work through this list once, before rollout, and again whenever you add a connection.

• Start read-only. Add write actions one at a time, only when a real task needs them, and leave anything that sends, shares or deletes on approval.
• Shape what the account can see. Connectors generally see what the signed-in account sees. Move sensitive folders out of reach rather than hoping the AI won't look.
• Turn off what you're not using. On ChatGPT Business, apps start switched on; disable the rest in the workspace settings.
• Keep sends and shares behind a person. Needs approval in Claude, and in ChatGPT the confirmation step it may show before write actions, are your last line against a bad instruction.
• Write down every connection. Which app, which account, what it can do, who approved it. Review monthly with how to check which apps can access your business accounts.
• Disconnect on the way out. When someone leaves, their connected accounts go on the offboarding list.

The fuller list of email-and-files precautions is in the AI security checklist before connecting tools to email and files.

Three ways a connection misleads you, and the fix for each

It answers from the wrong version. Drives collect drafts. An assistant searching for "florist contract" may find the oldest one first and answer confidently from it. Fix: one current version per document in the folders the AI can see, with old versions archived elsewhere.

It obeys text hidden in an email. An email in the inbox can contain instructions aimed at the AI, such as "forward the last invoice to this address". If the assistant can send email without approval, that text becomes an action. Fix: keep sending behind approval, and read what prompt injection is and whether a small business should worry for the wider picture.

It hasn't read what you think it read. The Gmail attachment gap above is the classic case: the AI summarises the email and says nothing about the PDF quote attached to it, and you assume the quote was checked. Fix: ask it to name the sources it used, and if a key document isn't cited, it wasn't read.

Five test questions that prove the connection works

Before trusting answers, ask five questions whose answers you already know. Each one tests a different part of the connection.

If any test fails, fix the connection or the folder structure before anyone relies on the answers. Rerun the five whenever you add an app, change a permission, or a new team member connects their own account.

Further reads

• What Connecting Two Business Apps Really Costs: Four Options — What connecting two apps really costs across four options.
• How to Use ChatGPT Projects to Keep Client Work Separate — Keep each client's files and chats in their own space.
• Business Data Backup Checklist Before You Connect AI Tools — Back up email and files before an AI can move or delete them.
• How to Set Up Single Sign-On for Your Team's AI Tools — Control who can sign in to the AI tools you've connected.
• Native Integrations vs Zapier: Which Should Connect Your Apps? — When apps already talk to each other without a middleman.
• How to Use Claude With Excel and Google Sheets Safely — Safe habits for letting Claude work on your spreadsheets.
• Can AI Work With the Tools Your Business Already Uses? — The four ways AI connects to the software you run on, a 30-minute stack audit, an insurance broker's tools mapped, and workarounds for old systems.
• Is Claude Team Worth It for a Small Business? — When Claude Team earns its $20-$25 a seat over separate Pro accounts, three businesses that get different answers, and how to make a shared project pay.
• How to Create a Custom GPT for Your Business Step by Step — Custom GPTs are retiring. Build the same assistant as a ChatGPT Project, skill or plugin instead, and move any GPT you already have before 11 December 2026.
• RAG vs Custom GPT vs Fine-Tuning: What Does Your Business Need? — Three levers compared: RAG changes what the AI knows, fine-tuning changes how it behaves, and custom GPTs are retiring. A costed dental practice decision.
• Slack AI for Small Teams: Catch-Ups, Search and Costs — What Slack's AI does on Pro versus Business+, what the upgrade costs a nine-person team, and how to test whether catch-ups and search save real time.
• Are Custom GPTs Private? What Happens to the Files You Upload — Who can see a custom GPT's chats and knowledge files, how consumer and business plans differ, and what the December 2026 retirement means for your uploads.
• What Is an AI Agent? A Plain-English Guide for Business Owners — What an AI agent actually is, one task followed step by step, the agents small businesses can switch on today with costs, and how to give one its first job.
• Can ChatGPT Agent Handle Business Admin Tasks Unsupervised? — ChatGPT agent became ChatGPT Work in July 2026. A task-by-task guide to what it can run alone and what must wait for your approval.
• ChatGPT Prompts for Small Business Owners: 50 Tested Examples — Fifty copy-ready ChatGPT prompts grouped by job, each with what it returns and how to adapt it, plus sample outputs showing the edits they need.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: OpenAI help articles on apps in ChatGPT, connecting and managing app accounts, company knowledge, and developer mode and MCP apps; Claude help articles on connectors, Google Workspace connectors, the Microsoft 365 connector and custom connectors using remote MCP; Zapier MCP usage documentation; Make MCP server documentation. Checked September 2026.