The problem: ChatGPT doesn't know anything about your business
Out of the box, ChatGPT is a capable general assistant with no idea what's in your inbox, your team's Slack channels, your CRM, or your GitHub repos. Ask it something that depends on your actual data — "what did we decide about the Q2 roadmap" or "summarize the last email from this client" — and it has nothing to work with beyond whatever you paste into the chat window. Every question that touches your business ends up requiring you to first go find the answer yourself, then paste it in for ChatGPT to reformat or reason over.
Custom connectors exist to close that gap: instead of a generic chat window, ChatGPT gets a live channel to a specific server that can search real content on your behalf, mid-conversation, without you copying anything in by hand. The setup is a one-time OAuth connection; the payoff is every future ChatGPT conversation being able to reach your actual data instead of working from what you happen to remember to paste.
This guide covers connecting ChatGPT to Great Arrow Digital as a custom connector, and what changes once it can search your workspace directly.
How it works
Great Arrow Digital exposes an MCP (Model Context Protocol) server at https://www.greatarrowdigital.com/api/mcp. ChatGPT connects to it as a web-based client using OAuth 2.1 with dynamic client registration and PKCE — you register the connector once and approve access through ChatGPT's own consent screen, rather than generating and pasting a token.
Once connected, ChatGPT can call tools against your workspace: searching memory, documents, and any integrations you've connected (Gmail, Drive, Slack, Notion, GitHub, and others). The MCP server's initialize response carries an instructions field specifically written to push search-before-answer behavior into connecting clients — so a connector-aware ChatGPT session leans toward checking your workspace before answering a question that references your specifics, rather than guessing or asking you to paste the answer in.
Setting it up
- Create your account. Sign up at /sign-up — no credit card required for the 14-day trial.
- Connect your business data sources first (optional but recommended). Anything ChatGPT should be able to search — Gmail, Drive, Slack, Notion, GitHub, and other supported integrations — needs to be connected to your account before ChatGPT can search it. You can also add these later; ChatGPT picks up new sources as soon as they're connected.
- Open the install page and choose ChatGPT. Go to /install, signed in, and select ChatGPT. This is a guided OAuth path.
- Enable developer mode in ChatGPT, then add a custom connector from Settings → Connectors → Add custom connector, pointing it at the endpoint the install page shows you.
- Complete the OAuth consent screen. ChatGPT walks you through sign-in and asks you to approve the connection — pick your workspace and approve.
- Confirm the connection. The install page can detect a successful OAuth connection automatically. If detection doesn't fire, a manual "I did this" confirmation is available.
- Test it. Ask ChatGPT something that depends on a source you connected — a recent email, a document, a Slack thread — and confirm the answer reflects real content rather than a generic response.
What "search before answer" actually looks like
Once the connector is live, a ChatGPT conversation that touches your specifics doesn't stay generic. Ask about a project, a decision, or a person your team has discussed, and ChatGPT is nudged to check your connected workspace before responding — pulling from memory, documents, or synced integration content rather than answering from general knowledge alone. This doesn't replace your judgment on what to connect: ChatGPT can only search what's actually in the workspace, so the more of your real data sources you connect, the more questions it can answer directly instead of asking you to supply the context yourself.
The range of "business data" here is broad by design. Beyond Google Workspace (Gmail, Drive, Calendar, Docs, Sheets, Slides) and Microsoft 365 (Outlook, Teams, OneDrive, SharePoint), the same account can connect developer tools (GitHub, GitLab, Jira, Asana, Linear), communication tools (Slack, Discord, Notion, Confluence), and CRM data (GoHighLevel). Each is connected independently in your integration settings, and once connected, ChatGPT's connector can search across all of them from the same conversation — you're not switching contexts to ask about an email versus a ticket versus a Slack thread.
Revoking access later
Disconnecting ChatGPT is a client-level action, separate from the data sources themselves. Removing the custom connector from ChatGPT's settings ends that client's access to your workspace without touching the underlying integrations — Gmail, Slack, and everything else stay connected and searchable from any other client you've connected. If you want to stop a specific data source from being searchable at all, that's handled separately, by disconnecting that integration from your account rather than by removing the ChatGPT connector.
Where to go next
If Notion is one of your team's primary knowledge sources, ChatGPT MCP Server for Notion covers connecting that integration specifically. If you also use Claude and want both clients working from the same connected data, Share Memory Between Claude and ChatGPT covers running both side by side.