Today3 stories

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 14The independent daily for Salesforce admins, developers and architects3 stories

Must-readAgentforce and AI

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?

RecommendedFlow and admin

Implementing email verification workflows in Salesforce beyond standard Validation Rules (opens in a new tab)

You will learn how to distinguish between email formatting checks and actual deliverability verification, and how to build a reliable workflow using Custom Fields, flows, and external APIs.

Why read this

The piece outlines trigger points, error handling, and monitoring metrics to maintain CRM data quality.

The article distinguishes between email validation, which enforces syntax through a Validation Rule, and email verification, which confirms domain existence, mail server configuration, and mailbox deliverability. Standard format checks cannot prevent bounces or identify disposable addresses.

It recommends placing verification at record creation, during field updates, or through bulk cleanup processes. A practical workflow involves creating a Custom Field, defining trigger events, calling an external verification service via API or managed package, and applying business rules to route verified, invalid, or risky addresses accordingly.

Developers are advised to handle inconclusive results gracefully, avoid redundant processing, maintain audit trails, and respect consent and privacy requirements. The author notes that while custom integrations offer flexibility, native applications can reduce maintenance overhead, and ongoing monitoring of bounce rates and verification metrics ensures the workflow actually improves data quality.

Read the original at dev.to (opens in a new tab)

Worth reading?

Flow and admin

Salesforce confirms MFA enforcement timelines and extension options for administrators (opens in a new tab)

Readers will learn the confirmed deadlines for mandatory multi-factor authentication and phishing-resistant requirements, along with how Salesforce plans to handle extension requests for non-compliant accounts.

Salesforce has clarified its ongoing multi-factor authentication rollout after conflicting messages caused confusion among customers. The company reaffirmed that mandatory multi-factor authentication remains required for all users by June 2026, with production enforcement beginning on July 20. Administrators and users with elevated permissions must use phishing-resistant methods.

Recent reports suggested enforcement might be delayed indefinitely or pushed past late October, but Salesforce explicitly stated there are no open-ended postponements. The platform is currently collaborating directly with a small group of customers who previously received extensions and require additional time to complete their security configurations.

A tool expected by mid-October will allow organizations to request ninety-day extensions for non-compliant users. Salesforce notes that over ninety percent of customers have already adopted the required controls and will contact any remaining accounts directly to ensure compliance within the next six to eight months.

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

Worth reading?