Best ChatGPT Plugins for Small Business (2026): Pricing, Permissions, and First Workflows

The best ChatGPT plugins for a small business are the fewest plugins needed to improve one repeated workflow. Start with one email-and-calendar stack, one system of record, or one document workflow—not a directory shopping spree. Installing a plugin is only the first gate: the included app must also be available to your plan and region, enabled by your workspace, authorized with the provider, and allowed to perform the requested read or write action.

For most teams, the safest first stack is Google Workspace or Microsoft 365 for inbox-to-follow-up, followed by Slack or HubSpot only when there is a measured need. Keep write actions behind approval during the pilot. A directory listing can be free to install while ChatGPT seats, Google Workspace, Microsoft 365, HubSpot, QuickBooks, Dropbox, Zapier, or other provider services still cost money separately.

The plugin is the package. Access still depends on every control layer beneath it.

What changed in the 2026 ChatGPT Plugin Directory?

The post-July-2026 plugin model is a new packaging system, not a revival of the retired 2023 marketplace under the same technical rules. OpenAI now defines a plugin as an installable workflow package that can contain a Skill, an MCP server or connected app, or both. ChatGPT and Codex share a universal public plugin directory on supported surfaces, although individual capabilities can still be surface-specific.

That creates five terms small businesses should keep separate:

• Plugin: the installable package people discover and select. It may bundle instructions, apps, templates, or interactive extensions.
• Connected app: the link to an outside service such as Google Drive, Outlook, Slack, or HubSpot. It exposes only supported information and actions through the authenticated account.
• Skill: reusable instructions, references, scripts, or templates that tell ChatGPT how to perform a workflow. A skill can work without connecting an outside service.
• Custom GPT: the earlier customized ChatGPT experience. OpenAI is transitioning custom GPT workflows to plugins. Instructions and knowledge can become a skill, but selected models, conversation starters, previous chats, and capability settings do not necessarily transfer as-is.
• Custom action: a REST API connection defined inside a custom GPT. OpenAI says custom actions do not transfer automatically; they need to be replaced with a supported app action or rebuilt as a custom MCP server.

The old 2023 plugin system was discontinued in 2024. Treat any guide that still tells you to switch to a “Plugins model,” enable a beta toggle, or browse the old Plugin Store as obsolete.

The practical verdict: choose a workflow, then choose the smallest stack

A plugin is worth installing only when it shortens a repeated task and leaves an auditable result. “We might use this someday” is not a workflow.

Use this order:

1. Name the repeated job and its owner.
2. List the minimum data the job needs.
3. Decide whether the first version can be read-only.
4. Confirm the exact plugin and included apps are visible in your workspace.
5. Connect a low-privilege provider account.
6. Require approval for messages, file changes, CRM updates, invoices, and financial actions.
7. Measure accepted outcomes, not generated output.

If the workflow needs three plugins and six connected services before anyone has tested one useful result, it is not a pilot. It is a small IT department wearing a fake moustache.

Best ChatGPT plugins for small business by first workflow

The table below is a selection matrix, not a claim that every listed capability is enabled for every account. Directory availability, supported actions, and plan or region requirements can change. Verify the live plugin detail page and permission screen before connecting business data.

Start with the row that matches an existing bottleneck. Do not install the whole matrix.

Google Workspace or Outlook: best first choice for inbox-to-follow-up

Choose the productivity suite your team already uses. The value comes from reducing context switching among email, calendars, and files—not from owning both ecosystems.

A conservative first workflow reads a defined inbox or label, identifies messages needing follow-up, checks the relevant calendar, finds an approved proposal or reference file, and drafts the next response. It should not send the email or change the calendar during the initial pilot.

Google Drive appears in the current public directory. OpenAI also documents Gmail and Google Calendar among supported apps for enterprise connection controls. Outlook Email appears in the directory, and Outlook Calendar is on the supported-app list. That still does not guarantee the same actions on every plan, region, surface, or workspace.

Slack: best for internal summaries, not autonomous posting

Slack is useful when a team repeatedly gathers updates from known channels and turns them into a short handoff, meeting brief, or blocker list. The current directory describes the plugin as able to “Read and manage Slack,” which is exactly why the first permission should be read-only.

Do not begin by allowing autonomous posts across a workspace. First prove that the summary captures the right channels, respects private-channel boundaries, links back to evidence, and saves enough time to justify the connection.

HubSpot: best for controlled CRM hygiene

HubSpot is a strong second plugin when inconsistent CRM records are already causing missed follow-ups or unreliable pipeline reporting. Begin with searches and exception reports: contacts without owners, deals without next steps, stale stages, or activities missing from a defined time window.

Move to approved writes only after the read-only report is accurate. Use test records, limit fields, and keep destructive merges or deletions out of the pilot. A plugin that confidently “cleans” the wrong CRM fields is just vandalism with excellent grammar.

QuickBooks and Stripe: useful, but financial writes need the tightest boundary

The directory listing found in this review is QBO Connector by Meridian, described as able to read and update QuickBooks. Small businesses should treat that as a third-party vendor connection and review the developer, privacy terms, scopes, and any connector charges before authorization. A directory presence is not the same as an Intuit endorsement.

Stripe also has a current listing. Use it first for reporting or preparation—not refunds, payment changes, or unsupervised financial actions. For invoice and estimate work, let the plugin assemble a draft from approved customer, item, and pricing data, then have a human compare totals, tax, payment terms, and recipient details in the source system.

Canva and Dropbox: lower-risk pilots when scope is narrow

Canva can turn an approved brief into a draft design, while Dropbox can find and organize business files. These are often easier pilots than finance or CRM because the team can work in a dedicated test folder or duplicate design.

The risk is still real. A connected app may receive relevant conversation context, and write access can create, edit, move, share, or remove content depending on the supported actions. Use a dedicated folder, approved brand assets, and versioned copies.

Zapier: powerful only after you verify the exact listing

Zapier can add a broad cross-app action layer through its own automation platform and MCP capabilities. Its official pricing documentation describes a task-based model, paid premium-app access, pay-per-task behavior on eligible plans, shared connections on Team, and stronger admin controls on Enterprise.

However, this review did not independently confirm a current Zapier listing in the signed-out public ChatGPT directory snapshot. Do not connect a lookalike or assume a third-party plugin has Zapier’s full capabilities. Verify the developer, included app or MCP server, scopes, pricing, and rollback controls in your own directory before using it.

What ChatGPT plugins cost in 2026

Directory installation may cost nothing while the working stack still has three separate bills: ChatGPT access, the connected-service subscription, and usage or transaction charges from that service.

OpenAI’s first-party pricing and help pages showed these US-dollar prices on October 21, 2026:

These are ChatGPT charges only. API usage is separate from Plus, and third-party services are not bundled simply because their plugin appears in the directory.

Provider costs should be budgeted as a separate line item. Google Workspace, Microsoft 365, Slack, HubSpot, QuickBooks, Canva, and Dropbox have their own seat or feature tiers. Stripe charges product and transaction fees. Zapier meters tasks and can add pay-per-task usage. Pricing is localized and changes frequently, so use the provider’s checkout or account page for the exact country, currency, billing term, tax, promotion, and feature tier.

Permissions: installation is not authorization

OpenAI’s current controls create a layered permission model:

1. Plugin availability: whether the bundle is visible or installed for the user or role.
2. Included skill access: whether its reusable instructions are available.
3. App access: whether the underlying connected service is enabled.
4. Provider authorization: which external account, files, channels, records, and actions that identity can access.
5. Action control: which read or write tools the workspace allows.
6. Approval policy: whether ChatGPT must ask before reading or acting.
7. Runtime controls: what the active ChatGPT or Codex surface can do after receiving data.

Depending on account and app, permission choices can include Always ask, Allow read actions, Allow low-risk actions, or Allow all actions. “Allow all” carries elevated risk and is not a normal starting point for a small-business rollout.

Sensitive actions include sending messages, changing files or records, modifying access, making purchases or financial transactions, and sharing sensitive information. Some requests can be denied rather than presented for approval.

Data exposure and terms to check before connecting

Installing a plugin can expose more than the final answer. OpenAI says enabled apps may receive relevant conversation context, relevant memories when Memory is on, and basic connection information such as IP address, browser or device type, language, region, and approximate location. The provider’s own terms, scopes, retention, residency, and privacy policy apply once the request reaches that service.

For ChatGPT Business, Enterprise, and Edu, OpenAI says information accessed through apps is not used to train models by default. For Free, Plus, Go, and Pro, app information may be used to train models when “Improve the model for everyone” is enabled.

Before connecting, record:

• the plugin developer and verification status;
• required and optional apps;
• requested OAuth scopes or shared credentials;
• folders, mailboxes, channels, objects, and fields in scope;
• supported read and write actions;
• whether content is synced/indexed or retrieved live;
• provider retention, residency, and subprocessor terms;
• OpenAI workspace data controls and applicable audit coverage;
• the exact disable, disconnect, and provider-revocation steps.

An admin-first rollout that a small team can actually maintain

Use one accountable owner for each plugin. That owner does not need to be a full-time IT person, but they do need authority to stop the workflow.

1. Inventory permissions before installation

Write down the data sources, connected identity, read actions, write actions, approvals, users, and downstream effects. Export the public catalog CSV if your eligible Enterprise workspace supports it; OpenAI notes that the export can be up to 48 hours old, so confirm the live plugin page too.

2. Start read-only where possible

Use Allow read actions or Always ask. Restrict the provider account to the minimum folders, channels, records, and roles. Do not use an owner or super-admin identity for routine testing.

3. Require approval for writes

Messages, invites, record updates, file changes, invoice creation, refunds, and payment actions should stay behind human confirmation. Keep “allow all” out of the first rollout.

4. Test with low-privilege accounts and disposable records

Use a test mailbox, a dedicated Drive or Dropbox folder, a private Slack channel, CRM test records, a QuickBooks sandbox or test company, and Stripe test mode where available. Confirm that denied access stays denied.

5. Inspect evidence, not just the answer

Capture the source links or record identifiers, approval prompts, created drafts, provider audit events, and ChatGPT compliance events available to your plan. OpenAI warns that app-log coverage depends on the app, product, and workspace configuration; absence from one log is not proof an action never happened.

6. Measure accepted outcomes

Count drafts that a person actually accepts with minor changes, correctly flagged CRM exceptions, minutes saved on approved work, error rate, and reversals. Do not count prompts, generated words, or “tasks completed” without checking business outcomes.

7. Define disable and revoke steps before launch

Document how to disable the plugin, disable the included app, disconnect the ChatGPT connection, revoke provider OAuth access, rotate any shared credential, turn off dependent automations, and identify records changed during the pilot. Disabling a plugin and revoking a provider connection are separate operations.

Three practical SMB pilot workflows

Pilot 1: inbox-to-follow-up

Stack: Gmail + Google Calendar + Drive, or Outlook Email + Outlook Calendar + the team’s file store.

Read: a defined inbox or label, upcoming meetings, approved proposals, and customer documents. Produce: a triage list and response drafts with source links. Approval: a person reviews recipients, promises, dates, attachments, and tone before sending. Success: at least 80% of selected drafts are usable after minor edits, with zero unauthorized sends.

Pilot 2: CRM hygiene

Stack: HubSpot, optionally Slack for an internal exception summary.

Read: stale deals, missing next steps, unowned contacts, duplicate candidates, and activities within a defined date range. Produce: an exception report first. Approval: permit only selected field updates after the report proves reliable; exclude merges and deletes. Success: accepted corrections increase while false positives and reversals remain below the team’s agreed threshold.

Pilot 3: invoice or estimate preparation

Stack: QBO Connector by Meridian or another verified accounting connection, plus approved Drive/Dropbox source documents; Stripe only when payment-link or invoice work is explicitly in scope.

Read: approved customer, item, quantity, rate, tax, and payment-term data. Produce: a draft estimate or invoice checklist, not an automatic final transaction. Approval: a finance owner verifies totals, tax treatment, recipient, dates, and terms in the source system. Success: preparation time falls without an increase in corrections, voids, refunds, or customer disputes.

A 14-day plugin test

A short pilot should end with a keep, narrow, or revoke decision—not permanent “testing.”

• Days 1–2 — Define: choose one workflow, owner, baseline, accepted outcome, and stop condition.
• Days 3–4 — Review: inspect the plugin developer, included apps, scopes, service terms, plan/region fit, provider costs, and rollback path.
• Days 5–7 — Read-only: connect a low-privilege account, use test data, and verify citations or record IDs.
• Days 8–10 — Draft: generate drafts or proposed changes without executing external writes. Track acceptance and errors.
• Days 11–12 — Approved writes: enable only the smallest necessary write actions, require confirmation, and inspect logs after each run.
• Day 13 — Failure drill: deny an approval, remove access, disconnect the account, and confirm the workflow stops cleanly.
• Day 14 — Decide: keep, narrow, or revoke based on accepted outcomes, errors, admin effort, total cost, and data exposure.

Methodology and verification limits

This guide was verified on October 21, 2026 using OpenAI’s public Plugin Directory, official plugin architecture, migration, permissions, admin-control, data-use, and pricing documentation, plus official provider pricing pages where referenced. First-party Google Search Console and GA4 evidence was unavailable and no performance claim was inferred from it.

We did not connect provider accounts or execute hands-on plugin actions. Directory listings, documentation, and pricing were reviewed editorially; exact actions, plan eligibility, regional availability, admin controls, provider scopes, and charges must be rechecked in the reader’s live workspace before rollout. Zapier’s current public-directory listing was not independently confirmed in the signed-out snapshot used for this review.

FAQ

Are ChatGPT plugins free?

Installing a directory plugin may be free, but the full workflow may require a paid ChatGPT plan, paid provider seats, transaction fees, task usage, premium assets, or a separate connector subscription. Never treat third-party charges as included with ChatGPT.

Which ChatGPT plan does a small business need for plugins?

OpenAI says the plugin directory is available across ChatGPT plans, but each plugin can depend on plan, region, workspace, role, surface, and included capabilities. A solo user can test eligible plugins on an individual plan; a team that needs centralized billing, workspace controls, and managed app access should evaluate ChatGPT Business or Enterprise.

Is a plugin the same as a connected app?

No. A plugin packages a workflow and can contain skills, connected apps, or both. The app is the connection to an outside service. Installing the plugin does not authorize the app or grant access beyond the connected provider identity.

Are the new plugins the same as the 2023 ChatGPT plugins?

No. The 2023 marketplace was retired. The 2026 model uses plugins as packages for skills and MCP-based connected capabilities across supported ChatGPT and Codex surfaces.

Can a plugin send emails or update records without asking?

Possibly, but only when the app supports the action and account, workspace, provider, and permission settings allow it. Approval behavior can range from always asking to allowing certain actions. Small businesses should keep messages, record changes, and financial actions behind approval during rollout.

How do I remove a plugin’s access?

Disable or uninstall the plugin, disconnect the app account in ChatGPT, and revoke the authorization in the provider. If shared credentials, automations, or dependent plugins are involved, disable those separately and rotate credentials when needed.

Does OpenAI train on data from connected apps?

OpenAI says app information is not used for model training by default for Business, Enterprise, and Edu. For Free, Plus, Go, and Pro, it may be used when “Improve the model for everyone” is enabled. Provider terms still apply to data sent to the connected service.

What is the safest first plugin workflow?

Use a read-only inbox, calendar, or file-summary workflow with a low-privilege account and human-reviewed drafts. It is easier to measure, easier to reverse, and less consequential than autonomous CRM, accounting, messaging, or payment writes.