By RamthaMedia
RamthaMedia Free eBooks · August 2026
Price: Priceless
· 14 min read
Preface
This book is for someone who already uses ChatGPT and has noticed the plugin directory without really exploring it — a freelancer, an ops person, a small team lead juggling inboxes, calendars, and a half-dozen other tools. By the end you will know how to connect an app properly, find the skills hiding under it, and decide what is worth keeping connected. It does not cover pricing or the developer side of building a plugin.
Chapter 1
The First App You Connect Sets the Tone for Everything After
A freelance operations consultant runs her week from four browser tabs — an inbox, a shared drive, a calendar, and a chat window she keeps open for everything else. She has heard that some of those tabs can be connected directly into the chat, but has never gone looking for how, and the word plugin makes her picture something for developers.
It isn't. Underneath the ChatGPT window sits a directory of connected apps, sorted into groups like Productivity, Creativity, Developer Tools and Communication. The ones marked Featured are the obvious starting point — Gmail, Google Drive, Outlook Email, GitHub, SharePoint, Slack — because they are the tools most people already have open in another tab.
Connecting one is a single button: open the app's own page in the directory, press Install, and it becomes something you can address directly in a conversation by name — @Gmail, @Notion, @GitHub, whatever it is. That one habit is the entire mechanism. There is no separate settings screen to learn first.
The first result is usually small and that is the point. Ask @Gmail to summarize what's sitting in the inbox, then ask it to draft a reply to one specific thread. The draft appears inside the same conversation, ready to send or edit, and the four tabs quietly become three.
What matters about this first connection isn't the app chosen — it's noticing that the pattern repeats. Every app in the directory works the same way: connect it once, then talk to it by name inside a normal conversation. Learn that once and the rest of the directory stops being intimidating and starts being a list of things worth trying.
That's the whole shape of a first hour with this: pick the app already causing the most friction, connect it, and ask it to do the thing you were about to do by hand. What starts to matter after that first small win is what else is hiding behind a name you already recognise — which is where a single app stops being one thing.
What you can actually do here
These are the uses that show up once an app is actually connected, not just listed on the directory page — organised by the kind of work each one clears off a desk.
Inbox and messages
| Use | Who it fits | Where | Worth knowing |
|---|---|---|---|
| Summarize a cluttered inbox and draft replies without opening a mail client | Anyone managing more email threads than they can read | @Gmail → ask for an inbox summary → ask it to draft a reply to one thread | Reply drafts stay inside the chat Only reads and drafts for the connected inbox, not others |
| Triage a Microsoft inbox and prep replies the same way | Anyone on Outlook instead of Gmail | @Outlook Email → summarize thread → draft reply or forward | Same pattern as Gmail, different mailbox |
| Read and organise a Slack channel's conversation without switching apps | Team leads catching up after time away | @Slack → ask it to summarize a channel or draft a message |
Calendars and meetings
| Use | Who it fits | Where | Worth knowing |
|---|---|---|---|
| Get a daily brief pulled from the actual calendar, not a guess | Anyone with a packed morning | @Google Calendar → Daily Brief skill | Named as its own skill, not folded into the general summary |
| Find a shared meeting slot across several people's calendars | Anyone scheduling with more than one person | @Google Calendar → Group Scheduler skill | Works within Google Calendar; a colleague on Outlook needs the Outlook Calendar plugin connected too |
| Deliberately open unscheduled time on a full day | Anyone whose calendar fills itself in | @Google Calendar → Free Up Time skill | |
| Arrive at a meeting already briefed on who's in it and what's pending | Anyone back-to-back all day | @Google Calendar → Meeting Prep skill |
Documents and knowledge
| Use | Who it fits | Where | Worth knowing |
|---|---|---|---|
| Turn a rough meeting into a structured spec someone can build from | Product and ops people who write specs from notes | @Notion → Meeting Intelligence, then Spec to Implementation | Two skills chained into one output |
| Search, summarize and update a Drive file without leaving chat | Anyone whose work lives across Docs, Sheets and Slides | @Google Drive → find the file → summarize the Doc, update the Sheet, or edit the Slides deck | One connector covers four Google apps It only reaches files already in Drive |
| Summarize a whole SharePoint site and flag who owns what | Anyone inheriting a messy shared drive | @SharePoint → summarize site or file → identify owner and status |
Building and shipping
| Use | Who it fits | Where | Worth knowing |
|---|---|---|---|
| Debug a failing CI check before it blocks a merge | Developers reviewing their own pull requests | @GitHub → CI Debug skill on the failing check | GitHub and GitHub Enterprise are separate apps under one plugin — the wrong one means the wrong repo |
| Prepare a reviewed change for publishing | Developers closing out a PR | @GitHub → Publish Changes skill | |
| Build and deploy a small web app from a description in chat | Non-developers who need a working site, not a mockup | Connect Vercel or Replit → describe the app → deploy | Deployment tools sit in Developer Tools, not Creativity — easy to miss if you never open that tab |
Sales, data and everything else
| Use | Who it fits | Where | Worth knowing |
|---|---|---|---|
| Pull CRM records into a conversation instead of opening the CRM | Salespeople checking a deal mid-call prep | Connect HubSpot, Attio or Salesforce → ask about a specific account | |
| Ask a plain question of product or business data | Anyone who wants an answer, not a dashboard | Connect PostHog, Mixpanel, Amplitude or BigQuery → ask the question directly | |
| Check a link or file for risk before opening it | Anyone handed a suspicious attachment or URL | Connect Malwarebytes or Bitdefender → ask it to check the link |
Chapter 2
One App Turns Into Several Skills Once You Look Closer
The directory's front page shows one line under each app's name. Google Calendar reads 'Manage Google Calendar events and schedules.' Notion reads 'Notion workflows for specs, research, meetings, and knowledge capture.' Neither line prepares you for what's actually sitting behind it.
Open Google Calendar's own page and the one line becomes five named skills: Google Calendar itself, Daily Brief, Free Up Time, Group Scheduler, and Meeting Prep. Each is something you can ask for directly and specifically, rather than hoping a general request lands on the right behaviour. 'Give me my Daily Brief' and 'help me find a slot with the team' are two different, named things — not two phrasings of the same request.
Notion works the same way, with four skills instead of five: Knowledge Capture, Meeting Intelligence, Research & Documentation, and Spec to Implementation. A meeting turns into notes, notes turn into a spec, and the spec turns into an implementation plan — three separate skills, each doing one clear step, chained by asking for them in order.
Google Drive goes further still. What the directory calls one connector is actually five: Google Docs, Google Drive itself, Google Drive Comments, Google Sheets, and Google Slides, all reachable through the single 'Google Drive' connection. Connect once and you've quietly gained access to four different Google apps, not one.
GitHub carries a version of the same idea from the other direction — it lists two separate Apps, GitHub and GitHub Enterprise, sitting under one plugin, alongside its own four skills: Review Follow-up, CI Debug, GitHub, and Publish Changes. Someone who only ever opens their personal repositories can go a long time without realising the Enterprise option is sitting right there.
None of this shows up until you open an app's own page rather than reading its line on the grid. The lesson carries forward: a plugin's one-sentence description on the directory is the smallest, safest version of what it actually does.
You may also like:
Everything ChatGPT Can Connect To
Chapter 3
Assembling a Personal Stack From Categories You Never Scroll To
A three-person agency is trying to run its whole operation — sales, delivery, and reporting — without hiring an ops hire yet. Each of those jobs has its own category in the directory, and none of them are the ones people usually browse first.
Business & Operations holds the CRM side: HubSpot, Attio, Salesforce, and Clay for connecting leads and pipeline directly into a conversation instead of clicking through a separate tab to check a deal. Data & Analytics sits next door, holding PostHog, Mixpanel, Amplitude and BigQuery for asking a plain question of the numbers rather than building a dashboard first.
Developer Tools carries the delivery side — GitHub for the code itself, Supabase for the database, Vercel and Replit for shipping something that actually runs. It also holds a genuinely surprising entry: Hostinger, listed here under the description 'Build websites by chatting,' sitting among database and deployment tools rather than anywhere near Creativity, where a website builder might be expected.
That placement is worth noticing on its own. The category someone browses first is rarely where the tool they actually need is filed. A small agency assembling a stack — one CRM connection, one analytics connection, one deployment connection — ends up pulling from three categories that have nothing to do with each other by name, but everything to do with each other by the job they're doing.
The stack itself isn't built in the directory. It's built by connecting each piece once, in whatever category it happens to sit in, and then addressing all three from the same conversation as the work moves between them — a lead confirmed in the CRM, a number checked in analytics, a page shipped through deployment, without opening a fourth tool to hold it all together.
What ties a stack like this together isn't the categories at all — it's a paragraph that appears on every single one of these pages, worded almost identically no matter which app it's attached to.
Chapter 4
What Connecting an App Quietly Hands Over
Every plugin's own page carries the same block of text near the bottom, regardless of whether the app is Gmail, Salesforce, or a niche tarot-reading tool three categories deep. It is worth reading once carefully, because after that it stops being surprising and starts being something to plan around.
When an app is connected, relevant chats and memories may be shared with it to provide context for requests made to it. That sharing runs in the direction of giving the app what it needs to answer well — a calendar app needs to know what's being scheduled, an email app needs to know what's being replied to.
The reverse direction is stated too: if Memory is enabled, data coming back from a connected app may be used to proactively surface information or suggestions later, in conversations that have nothing to do with that app. And each app's own use of whatever it receives is governed by its own separate terms and privacy policy — connecting an app does not fold its data practices into ChatGPT's.
The Google-specific version of this note is more precise than most: data synced from Google apps may be used to provide relevant, personalised information, but is not used to train generalized models, except for anything explicitly submitted as feedback or included directly in a response. Deleting a conversation also deletes whatever app data was pulled into that specific conversation.
One line covers every app without exception: use of apps may come with elevated risk, and connections can be reviewed or removed at any time from settings. It isn't a warning attached to one risky plugin — it's the same sentence attached to all of them, which is itself worth noticing. The book doesn't need to guess at which connected app deserves more caution than another, because the directory itself doesn't distinguish between them either.
None of this argues against connecting anything. It argues for treating every connection the same way — worth having for what it saves, worth reviewing later for what it's actually been asked to do.
You may also like:
The NoteGPT Habit From First Upload to First Bill
Chapter 5
The Day One Plugin Stops Covering the Whole Job
Somewhere in a busy week, one connected app stops being enough on its own. A Tuesday with six back-to-back meetings needs more than a Daily Brief — it needs a brief in the morning, prep before each call, and a plan for whatever unscheduled time exists between them. That's three of Google Calendar's five skills, asked for in sequence rather than one being treated as the whole feature.
The same pattern shows up sideways, across apps rather than within one. A lead confirmed in a CRM connection often needs a follow-up email drafted through a mail connection, and a meeting prepped through a calendar connection — three separate apps doing three separate, small jobs inside what feels like one piece of work.
Some of the directory's categories only get found this way, by need rather than by browsing. Healthcare, Travel, Finance, Security, and Education & Research are all real categories — Healthcare holds nutrition and fitness data tools, Travel holds flight and trip planners, Security holds link and file checkers — but none of them sit on the homepage the way Productivity and Creativity do. They're reached by selecting the category directly, which most people only do once they already know, by name, what they're looking for.
That's a fair description of most of the directory past the first two rows: not hidden exactly, just organised for someone who already knows the job they're trying to solve, rather than someone browsing for ideas. A reader who has only ever used the Featured row has seen a fraction of what's actually connectable.
The moment one plugin stops covering the whole job is usually the moment worth treating as a prompt to look sideways — not for a bigger single tool, but for the next small, specific connection that covers the part the first one doesn't reach.
Chapter 6
Deciding Which Connections Are Worth Keeping
Months into using several connected apps, most people have a longer list than they remember building — one connected on a whim, one tried once and forgotten, one still doing real work every day. Reviewing that list is worth doing on purpose rather than by accident.
The directory has an entire category for exactly this kind of drift: Other, sitting at the very end past Entertainment, holding whatever doesn't fit anywhere else — Etsy for shopping, a general Podcast App for finding shows. Nothing wrong with either, but their placement says something true about most connected-app lists: a few entries end up there simply because they were interesting once, not because they're used.
Every connection can be reviewed or removed from settings at any time — the same line that appears on every plugin's own page turns out to be the exit as well as the disclosure. Removing an app doesn't touch what it already did inside past conversations; it only stops it from being asked to do anything new.
A reasonable way to decide what stays: does asking this app for something save an actual step, or does it just feel like it should? The Gmail connection that drafts a reply every day earns its place. The tarot or trivia plugin connected out of curiosity during a slow afternoon rarely gets asked a second question.
None of this needs to happen all at once, and there's no penalty for a directory left half-explored. The whole value of this system is that it grows with whatever gets connected — one app at a time, kept for as long as it earns the tab it replaced, and let go the moment it doesn't.
Questions readers actually ask
Do I need to install anything on my computer to connect one of these apps?
No — connecting happens inside the directory itself. Opening an app's own page and pressing Install is the entire process; nothing downloads outside the browser.
Can I connect more than one app at the same time?
Yes. Each connection is separate and independent, and there's no stated limit on how many can be connected at once — the directory covers dozens of categories on the assumption that several might be connected together.
What does mentioning an app with @ actually do?
It addresses that specific connected app directly inside the conversation, the same way you'd name a person to get their attention — the request that follows is handled by that app rather than by a general response.
If an app has several skills listed, do I have to name the skill exactly?
The skills are named on each app's own page — Daily Brief, Meeting Prep, and so on — and asking for one by that name is the clearest way to get it, though the underlying request can be phrased naturally around it.
Does connecting an app mean it can read everything in my account?
The stated scope is tied to what the app needs to answer requests made to it — a calendar connection is described as reaching events and schedules, not unrelated parts of the same account.
Will a connected app remember things about me in later conversations?
Only if Memory is enabled — the directory states that data from a connected app may then be used to proactively surface information later. Without Memory turned on, that carry-over doesn't happen.
Is my data used to train ChatGPT's models once an app is connected?
For Google apps specifically, the stated position is no — data synced from them isn't used to train generalized models, except anything explicitly submitted as feedback or included in a response.
What happens to app data if I delete the conversation?
Deleting a conversation is stated to also delete whatever app data was pulled into that specific conversation.
Can I disconnect an app once it's connected?
Yes — every plugin page states that connections can be managed or removed at any time from settings.
Are GitHub and GitHub Enterprise the same connection?
No — they're listed as two separate Apps under the one GitHub plugin. Which one is active in a given conversation is worth confirming rather than assuming.
Why can't I find categories like Healthcare or Security on the homepage?
They exist as full categories but aren't part of the Featured row shown by default — they only appear once that specific category tab is selected.
Does the Google Drive connection cover Google Sheets and Slides too, or just Drive itself?
One Google Drive connection is described as covering Docs, Drive, Drive Comments, Sheets and Slides together, rather than requiring a separate connection for each.
Is there a cost to connecting these apps?
The directory page itself doesn't state pricing for connecting apps — that detail isn't part of what's covered here.
Cover photo: Photo by https://kaboompics.com/ on Pexels. Illustrative image — not a screenshot of the site described.
Official source links:
ChatGPT
Disclaimer: This eBook is compiled from publicly available information and was accurate at the time of writing. For full and up-to-date details, please visit the official website linked above. RamthaMedia accepts no legal liability for any decision made on the basis of this eBook, and nothing here is professional, financial or legal advice.
