The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Connecting ChatGPT and Codex to Salesforce through plugins and the DX MCP (opens in a new tab)

Readers will learn how to securely link ChatGPT and Codex to Salesforce data and development environments using official plugins and the DX MCP connector.

Why read this

The piece also outlines model selection strategies and permission handling to keep workflows reliable.

OpenAI Salesforce Integrations

  • External data plugins
  • Agentforce Sales app plugin
  • Tableau plugin
  • Salesforce DX MCP connector
Key plugins and connectors linking OpenAI tools to Salesforce workflows

The article is a guide to OpenAI’s product line and how Salesforce professionals can connect it to their work. It explains that ChatGPT is now delivered mainly through a desktop app that combines chat with Codex, and introduces ChatGPT Work, an agentic mode that carries out multi-step tasks across Connected Apps and files. It also covers Codex, OpenAI’s coding agent available through the CLI, IDE, desktop and web; Dots, always-on autonomous agents that can run tasks after a chat ends and can even coordinate Codex work; ChatGPT inside Slack and Microsoft Teams; and the Spaces, Pages and Sites tools for shared projects, interactive documents and live web apps built from Codex.

On features, the piece describes plugins as the means of giving the AI access to external data, with the Salesforce plugin (formerly the Agentforce Sales app) letting users read and edit CRM records from ChatGPT while respecting their existing Salesforce permissions. A Tableau plugin offers similar access to Tableau sites, workbooks and metrics. For developers, the official Salesforce DX MCP connects Codex to more than 60 developer tools, such as listing orgs, retrieving metadata, creating snapshots and running tests, and it is hosted and updated by Salesforce. Skills are reusable instruction sets, AGENTS.md files give standing instructions read before work begins, projects group related conversations and files, and team tasks let several people own and manage a task. The author explains three model tiers: Astra, the most powerful and costly, to be used sparingly; Sol, the everyday model for moderately complex work; and Luna, the fast, cheap model for simple tasks. The key advice is to match the model to the task, since a weak model on a complex job can waste tokens without a result.

The article offers admin use cases such as generating project and org documentation, summarizing customer and deal information before meetings, and using Codex with the DX MCP to build metadata, testing in a Scratch Org or sandbox, and deploying only after review. Throughout, the author stresses that AI output must be verified, that AI is an assistant rather than a replacement for skilled Salesforce professionals, and that agentic tools should be given restricted org access, with deployments handled manually. Users of the Salesforce app should also be told that AI can make mistakes, and people should avoid granting AI more access than it needs and check their permission and security setup before connecting tools.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Recommended

Building a custom Apex tool for Lead conversion with Salesforce Model Context Protocol (opens in a new tab)

You will learn how to configure a Salesforce Model Context Protocol server and write an Invocable Apex class to handle Lead conversion through AI agents.

Why read this

The piece clarifies why generic record mutation tools cannot replace the native conversion process.

Introduces Salesforce Headless 360 and the Model Context Protocol as methods for AI agents to interact with orgs. Explains that basic access is free but may consume Flex Credits.

Walks through creating a custom MCP server in Setup and notes that default tools do not support Lead conversion. Details the architectural reason why generic SObject mutation tools fail for this task, citing atomic execution, field mapping, deduplication, and related record reparenting.

Outlines the requirement to build an Invocable Apex class using Database.convertLead(). Describes the necessary annotations and access modifiers needed to expose the method to the MCP framework.

Read the original at Salesforce Break (opens in a new tab)

Worth reading?