Connecting a plugin is not the same as giving Codex access. That distinction is the difference between a system that works and one that looks like it works — until you ask it to do something real.
Most business owners click "connect Gmail," get the green checkmark, and move on. Then they ask Codex to pull their 12-month proposal history and either nothing comes back or Codex generates a confident-sounding answer that has no basis in their actual inbox. The plugin handshake completed. The data access was never real. And now you're building on a blind spot.
This post covers Step 10 of the Codex setup sequence: installing plugins, connecting them correctly, and — most importantly — running the verification step that almost everyone skips.
For the complete setup framework, read the full guide.
Why Plugins Come Before Any Real Work
Without plugins, Codex is operating in a vacuum. It has no access to your email, your files, your calendar, your payments, or your meetings. It can answer general questions, but it cannot do anything specific to your business. It is, in practical terms, blind.
Plugins are the connectors between Codex and your actual business data. Gmail, Google Drive, Google Calendar, Stripe — these are not nice-to-haves. They are the sources of everything Codex will learn and act on. Until they are connected and verified, no intelligence-gathering skill, no operational task, and no business-specific automation is possible.
This step belongs here — after permissions, after sandbox setup, after your storage strategy is decided — because those earlier steps create the environment plugins need to function reliably. If you skipped ahead, go back. The sequence matters. Read more about permissions setup before proceeding if you haven't completed that step.
Watch me explain this live to see the plugin connection process walked through in real time.
How to Connect Plugins: The Mechanics
The process is straightforward. Inside Codex:
- Click the Plugins section in the sidebar
- Find the plugin you want to connect
- Click the "+" icon next to it
- Log in with the relevant account credentials
- Authorize the connection when prompted
Do this for each plugin. It takes a few minutes per connection. The authorization screen will vary by service — Gmail will ask you to approve specific permissions, Stripe will require your account login, and so on. Read each authorization screen before clicking through.
That's the easy part.
The Plugins Worth Connecting First
Not all plugins carry equal weight. Some unlock capabilities that are central to running Codex as an operational system. Others are useful but secondary. Here is how to prioritize:
| Plugin | Priority | What It Unlocks |
|---|---|---|
| Gmail | High | Email access for research, proposal tracking, outreach, revival campaigns |
| Google Drive | High | File and document access across your business |
| Google Calendar | High | Scheduling context, meeting history, time pattern analysis |
| Stripe | High | Payment and revenue data for financial reporting |
| Cloudflare | High (if building) | Website, landing page, and app deployment — one of the most agent-forward integrations available |
| Fireflies | Medium | Meeting transcriptions — noted as inconsistent in reliability |
| Otter AI | Medium | Alternative meeting notes source |
| Canva | Low | Creative assets — largely redundant once you discover Codex's native image generation |
Google Workspace integrations (Gmail, Drive, Calendar) are your first priority because they are where most of your business intelligence already lives — in emails, documents, and meeting records. Stripe is close behind if you want Codex to understand your revenue patterns.
Cloudflare deserves a callout: if you are building anything with agents — websites, landing pages, client-facing tools — Cloudflare is one of the most agent-forward options available. A free plan exists, and the paid tier starts at $5/month.
On Canva: I connected it and have never used it since discovering what Codex can do natively with image generation through the ChatGPT 2.0 images skill. Connect it if you want, but don't prioritize it.
On Fireflies: it is listed as a plugin, but reliability has been inconsistent in my experience. If you rely on meeting transcripts for business intelligence, consider migrating toward Google Meet, where recordings and transcripts are more reliably accessible to agents. This is a migration I am actively making in my own business.
The One Limitation You Need to Know Upfront
Currently, Codex only supports one connected email account per plugin. If your business operates across multiple Gmail accounts — a personal account, a business account, a team account — you can only connect one through the standard plugin flow.
A separate process exists for adding multiple Gmail credentials manually. That will be covered in a dedicated video. For now, connect your primary business email account and understand this is a known limitation, not a bug.
The Step Almost Everyone Skips: Verification
Here is what I call the Proof Protocol: don't trust the confirmation screen. Don't accept Codex's self-report when you ask it whether it has access. Make it prove it with real data.
The confirmation screen tells you the handshake completed. It does not tell you how deep the access goes, whether the integration is pulling live data or a shallow cached summary, or whether Codex can actually retrieve the specific information you need to run your business.
The test is simple. After connecting each plugin, ask Codex a specific, data-dependent question:
- Gmail: "Pull the last five emails I received from anyone I sent a proposal to in the last 90 days."
- Google Drive: "Find the most recently modified document in my Drive and tell me its title and last edit date."
- Google Calendar: "What meetings do I have scheduled in the next seven days?"
- Stripe: "What was my total revenue last month?"
If Codex retrieves actual, accurate data — the plugin is functioning. If it stalls, deflects, or produces a generic non-answer, the connection is cosmetic and you have a problem to solve before moving forward.
Asking "do you have access to my Gmail?" is not the test. Any system will say yes. Asking it to retrieve something specific and verifiable — that is the test.
This is important enough that it has its own dedicated step in this series. Learn more about plugin verification for the full breakdown of how to run this correctly across every connected plugin.
What to Do When a Plugin Fails Verification
If verification fails, you have a few options:
Re-authorize the connection. Disconnect the plugin and reconnect it. Some connections drop during initial setup if the authorization window times out.
Check the permission scope. Some plugins offer limited permission options during authorization. If you only granted read access to a subset of your Gmail, Codex may not be able to reach the emails you need. Reconnect and approve broader permissions.
Investigate API access. Some integrations are shallow by design — they provide a summary layer rather than direct data access. If the plugin cannot get you what you need, Codex can help you explore API-level access for that tool. This is a more technical path, but it is worth knowing it exists.
Evaluate whether the tool is the right tool. If a plugin consistently fails to provide reliable access, that is information about the tool's agent-friendliness, not about Codex. Some tools were not built with agent access in mind. Read the full guide for more on evaluating tools on the agent-friendly spectrum before investing in a broken integration.
Common Mistake: Treating the Checkmark as the Finish Line
The business value of Gmail plugin access is significant. Consider a single prompt: "Review the last 12 months of emails, identify everyone I sent a proposal to, note who closed and who didn't, and build a strategy to revive the ones who went dark." That is a powerful, actionable task that would otherwise take hours of manual review.
But that task is only possible if the Gmail connection is real, not cosmetic. A checkmark that precedes a hallucinated answer is worse than no connection at all — because it hides the problem while you build on top of it.
Verify every plugin before you move on. Sixty seconds per plugin. It is the fastest diagnostic step in this entire setup sequence.
Where This Fits in the Full Setup Sequence
Plugin installation and verification sits at Step 10 for a reason. By this point you should have:
- A functioning sandbox with full permissions
- A cloud storage strategy in place
- Named environments set up for your projects
- Computer Use and Browser Use enabled
If any of those are incomplete, the plugin connections will be surface-level at best. The plugins need a functional environment to operate inside. Build the environment first, then connect the data sources.
After plugins are verified, you move to Skills activation and the Business Intelligence Gathering Skill — where Codex reads everything it now has access to and begins building a real model of your business. Learn about the Business Intelligence Gathering Skill to understand what becomes possible once this step is complete.
The Principle Worth Carrying Forward
Connection is not access. Access is not verified access.
Every plugin connection is a claim. Treat it like one — and make the system prove it before you build anything on top of it.
— Shanee
*
This article is promoted by: linkedin-posts/post-11.md
Use the prompts behind this system
The Growth Academy Skills Dashboard includes 100+ Codex skills and prompts for SMB owners.
See the Skills Dashboard →