Skip to content
Connector Scout
–saved records

ChatGPT · Salesforce

Does Salesforce connect to ChatGPT?

Yes, for reading and analysing CRM data. OpenAI lists a Salesforce-built Salesforce plugin for ChatGPT that reviews accounts, opportunities, contacts and activity, summarises pipeline, stalled deals and forecast risk, drafts follow-ups, and turns call notes and next steps into structured updates for the CRM workflow. OpenAI does not enumerate which Salesforce objects or fields the plugin can write, so treat CRM writes as unconfirmed and keep changes under human review inside Salesforce.

Verified availableDocumentation verifiedLast verified 10 Aug 2026Native app
Compare connections

Quick answer

Yes — Salesforce connects to ChatGPT as a native app, verified against official documentation on 10 Aug 2026. Documentation confirms read and search access, while create, update, delete and interactive remain not confirmed — which is different from unavailable. Yes, for reading and analysing CRM data. The main documented limit: openAI does not enumerate which Salesforce objects or fields the plugin can write, so CRM writes are unverified here.

Relationship
Official and documentation-verified
Confirmed access
Read and Search · create, update, delete and interactive not confirmed
Plan or account
A ChatGPT account on a plan where plugins are available
Setup and admin
ChatGPT Plugin Directory + Salesforce authentication
Last verified
10 Aug 2026
Best fit or limit
OpenAI does not enumerate which Salesforce objects or fields the plugin can write, so CRM writes are unverified here.

What it is

OpenAI's Plugin Directory lists Salesforce as a plugin made by Salesforce, invoked in ChatGPT with prompts such as @Agentforce Sales. The documented value is review and synthesis: pulling account, opportunity, contact and activity context into a conversation, summarising pipeline health, stalled deals and forecast risk, and drafting the follow-up communication that comes out of a call. OpenAI also describes turning notes and next steps into structured updates for the CRM workflow, but the page does not list writable objects, fields or approval behaviour, which is why Connector Scout records create and update as not-confirmed rather than supported. Salesforce permissions still apply: the plugin reaches what the authenticating user can already open.

Connection type First-party Salesforce plugin for ChatGPT, built by Salesforce

What it can do

What it cannot do

Not confirmed means official documentation does not assign this capability to this specific connection. It is not a claim that the capability is impossible.

Every status is defined the same way across the site — see how connector capabilities are defined and evidenced.

Availability and requirements

OpenAI lists the Salesforce plugin in its Plugin Directory as made by Salesforce. As with every ChatGPT plugin, OpenAI states that availability and capability vary by plan, workspace, role, surface and region, and Business and Enterprise workspace admins control which plugins members may use.

Account requirements

  • A ChatGPT account on a plan where plugins are available
  • Workspace admin enablement for Business, Enterprise or Edu workspaces
  • A Salesforce user account with access to the accounts, opportunities and activity in scope

How to connect

Setup path ChatGPT Plugin Directory + Salesforce authentication

  1. 1. Confirm the plugin is allowed

    In a Business, Enterprise or Edu workspace, check that an admin has enabled the Salesforce plugin for your role.

  2. 2. Add Salesforce from the Plugin Directory

    Open the Plugin Directory in ChatGPT and connect the Salesforce plugin.

  3. 3. Authenticate as the right Salesforce user

    Sign in with the Salesforce user whose profile and sharing rules should define what ChatGPT can see.

  4. 4. Invoke it in a prompt

    OpenAI documents prompts addressed to the plugin, for example @Agentforce Sales.

Permissions, privacy, and admin controls

ChatGPT plugins are managed by workspace admins: apps are enabled by default for Business workspaces and disabled by default for Enterprise and Edu, which use role-based access controls. On the Salesforce side, connecting the plugin authenticates a Salesforce user, so a Salesforce administrator should confirm which profile is used.

  • CRM data is commercially sensitive: pipeline, forecast and contact detail enter the ChatGPT conversation whenever the plugin is used.
  • Because write scope is undocumented, review anything the plugin proposes as a CRM change inside Salesforce before treating it as applied.
  • Enterprise and Edu workspaces can restrict the plugin by role; Business workspaces have plugins enabled by default.
  • Salesforce field-level security and sharing rules are the effective boundary, so scope the authenticating profile deliberately.

Platform context

  • OpenAI’s Plugin Directory is now the main discovery surface, while apps remain the integrations that connect ChatGPT to external data and actions. App capabilities and availability can vary by app, plan, workspace, role, surface, model, and region. Business workspace admins can manage apps; apps are enabled by default for Business and disabled by default for Enterprise/Edu. Enterprise/Edu can use role-based access controls. ChatGPT permissions do not give an app new provider permissions; they govern when ChatGPT asks before using access already granted. Voice mode does not currently support apps.

Documented limitations

  • OpenAI does not enumerate which Salesforce objects or fields the plugin can write, so CRM writes are unverified here.
  • No approval or confirmation behaviour for CRM changes is documented on the plugin page.
  • Varies by app, plan, workspace, role, surface, and region; confirm in the current Plugin Directory.
  • The plugin reaches only what the authenticating Salesforce user can already open; profiles, sharing rules and field-level security still apply.
  • Connector Scout has not verified Claude or Gemini Salesforce connections, because neither vendor documents one at the same first-party standard.

Best use cases

  • Building an account brief from Salesforce accounts, opportunities, contacts and activity
  • Summarising pipeline health, stalled deals and forecast risk
  • Drafting follow-up communication after a call
  • Turning call notes and next steps into a structured summary for CRM updating

Example prompts

  • “@Agentforce Sales summarise my open opportunities and flag any that have not progressed in three weeks.”
  • “Review this Salesforce account's recent activity and give me a one-page brief before tomorrow's call.”
  • “Where is forecast risk concentrated in my pipeline this quarter, and why?”
  • “Draft a follow-up email from these call notes and list the CRM next steps it implies.”

Troubleshooting

  • The plugin is not available

    Plugin availability varies by plan, workspace, role, surface and region; in Enterprise or Edu workspaces an admin must enable it for your role.

  • Records are missing from an answer

    The plugin inherits the authenticated Salesforce user's access. Check profiles, sharing rules and field-level security for the records in question.

  • A CRM update did not appear in Salesforce

    OpenAI documents structured updates for the CRM workflow but no object-level write scope. Verify in Salesforce and apply the change manually if it is absent.

Official sources

Verification history

Last verified 10 Aug 2026 · next review 10 Sept 2026 · Connector Scout editorial research

  1. 10 Aug 2026First verification. OpenAI publishes a Salesforce plugin page describing CRM review, pipeline summarisation and follow-up drafting; write scope is not enumerated per object, so create and update are recorded as not-confirmed.

Documentation verified — editorial disclosure

Documentation verified means Connector Scout confirmed the connection and listed capabilities against official provider documentation. It does not mean Connector Scout completed hands-on testing in a live account.

Independence notice

Connector Scout is not affiliated with OpenAI or Salesforce. Confirm security-sensitive details against the vendor’s own documentation before rolling out access.