Connect Salesforce so Grok can query and update CRM records

Salesforce is a built-in Grok connector. After setup, Grok can explore objects, search and filter records, create Leads / Opportunities / Accounts / Cases (and custom objects), and update fields — all under your Salesforce user’s permissions, sharing rules, and field-level security. Official guide: Salesforce connector.

Admin setup (console)

On Grok Business and Enterprise, a team admin provisions the connector before members see it:

1. Open console.x.ai and go to Grok Enterprise → Connectors (or Grok Business → Connectors per your console labels).
2. Add the Salesforce connector.
3. Provide the OAuth credentials (Client ID, Client Secret) in the setup flow.
4. Follow any remaining admin steps the console shows, including the documented Salesforce DX MCP Server (Beta) install/configure reference on the Salesforce guide when your org requires it.

Members cannot finish personal OAuth until admin provisioning completes.

Connect as a team member

1. Go to grok.com/connectors.
2. Click New Connector and search for Salesforce.
3. Sign in with your Salesforce credentials and approve the requested permissions.

OAuth scopes the docs list: mcp_api (REST and SOAP APIs for read/write) and refresh_token (session refresh). Grok never exceeds what your connected Salesforce user can see or modify.

What to ask

Docs’ examples include:

• Show me the top 10 closed deals for this week
• What Opportunities are closing this month over $50k?
• Create a new Lead for Jane Smith at Acme Corp
• Show my recent cases that are still open
• Summarize the Account history for Globex Corporation

Ask in normal chat once the connector shows as connected.

Privacy and disconnect

Official privacy points: xAI does not use Salesforce data for model training; Grok queries Salesforce in real time and does not copy or store your records on xAI servers; permissions stay enforced. Currently one Salesforce org/instance per team.

To disconnect:

1. Open grok.com/connectors.
2. Find Salesforce and click Disconnect.

Pitfalls

• Business/Enterprise admin provisioning comes first; consumer self-serve may not see Salesforce until your plan and console allow it.
• One org per team — switching instances needs a disconnect and reconnect plan with your admin.
• Create and update calls follow your Salesforce profile; a permission error usually means the Salesforce user lacks the field or object, not a Grok bug.