Loading
Connect in real time with the Trailblazer Community in Slack Open BetaRead More

Sales Cloud in Claude (Beta)

Publish Date: Oct 20, 2026
Description

What Is Sales Cloud in Claude?

Bring Salesforce directly into Claude with a ready-to-use experience built for sellers. Sales Cloud in Claude combines live Salesforce data and trusted business context with prebuilt sales skills, enabling sellers to reason over their business, keep pipeline up to date, and take action, all without leaving Claude.

These skills were built by Salesforce and Anthropic, engineered specifically to draw on Claude's reasoning, agentic tool use, and generative UI, not generic CRM prompts wrapped around an API, but capabilities that extend what Claude can do. This includes an onboarding experience that reads a seller's enterprise context, Salesforce, Slack and any connector in Claude, to stand up a tailored dashboard, with their accounts, pipeline and live data, surfaced in interactive views Claude generates.

Sales Cloud in Claude is currently available in beta. Request access to join the beta and experience how Salesforce and Claude can help your sales teams get work done where they already work.

Resolution

Beta Licensing Requirements

A Salesforce Enterprise Edition (EE+) license and a Claude Teams or Enterprise license agreement with Anthropic are required to use Sales Cloud in Claude. Packaging and pricing details will be confirmed ahead of General Availability (GA).

Requesting Access: The Beta Signup Process

Find the Sales Cloud in Claude listing on AgentExchange to start the signup process.

How Do I Troubleshoot Salesforce in Claude?

Why do I see "OAUTH_APPROVAL_ERROR_GENERIC" on the Salesforce login page?

  • Cause: The ECA is missing required OAuth scopes.
  • Fix: In the ECA, enable these scopes:
    • Access Salesforce hosted MCP servers (mcp_api)
    • Perform requests at any time (refresh_token, offline_access)

Why does Claude show "Authorization with [Connector Name] failed"?

  • Cause: The External Client App (ECA) is disabled, or the user isn't permitted to use it.
  • Fix:
    1. Confirm the ECA isn't disabled.
    2. Check the ECA policies.
    3. Make sure the user has a selected profile or an assigned permission set.

Why does Claude say "Couldn't connect to the server" after I authorize?

  • Cause: The Headless360 (H360) MCP server isn't activated.
  • Fix: Activate the H360 MCP server, then reconnect.

Why is the "Salesforce Servers" tab missing under MCP Servers?

  • Cause: The org doesn't have the MCPService_Permission.
  • Fix: Contact Salesforce Support to have the permission added.

Why does one user get a 401 "INVALID_SESSION_ID" error when others in the org can query?

  • Cause: "Session Security Level Required at Login" is set at the profile level. This is a known limitation.
  • Fix: Assign session security through a permission set instead of the profile.

Known Limitations

  • Skills are out-of-the-box and can't be customized within the standard plugin. You can ask Claude to customize out-of-the-box skills for your environment.
  • Claude may update fields that your Salesforce automation normally controls (for example, closing an Opportunity that normally requires approval). Review your permissions and validation rules.
  • If you plan to enable writes with the MCP server’s Dispatch API, ensure you review the release note Create and Update Records in Salesforce in Claude (Beta) first.

How to Get Access and Get Help

  • Have a sales, licensing, or packaging question? Contact your Salesforce Account Executive.
  • Are you in the beta and need setup assistance? Log a case with Salesforce Support. Select 'Sales' as the Product and 'Claudeforce' as the Topic.
  • Have a question not covered here? Stay tuned — more guidance is coming as we approach General Availability (GA).
Knowledge Article Number

005460096

 
Loading
Salesforce Help | Article