Today9 stories

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 39The independent daily for Salesforce admins, developers and architects9 stories

Must-readArchitecture

Threat actors are using the ARTEX framework against Salesforce orgs; here is how to defend (opens in a new tab)

You will learn how an AI-driven attack against Salesforce environments behaves, what Salesforce Threat Intelligence has observed, and which controls to put in place now.

  1. Use stolen application credentials
  2. Relay traffic through Apex and Named Credentials
  3. Inspect existing Apex and integration settings
  4. Deploy custom Apex and REST endpoints
  5. Enumerate users, profiles and Permission Sets
  6. Retry code-execution and integration paths
How the ARTEX-assisted campaign moved through a Salesforce org, from access to persistence

Salesforce Threat Intelligence reports that several threat actors are using ARTEX, an open-source, multi-agent offensive framework originally built for autonomous penetration testing. A malicious operator supplies a target and an objective, and AI agents coordinate the intrusion, combining known attack techniques with continuous planning, parallel execution and on-the-fly code generation. The framework’s GitHub repository was taken down, but community forks still circulate, and the authors treat ARTEX as an accessible capability rather than a tool tied to one actor. Other vendors report its use by a state-aligned actor against Microsoft 365 tenants and by financially motivated groups against financial organizations.

Salesforce observed a campaign that used stolen application credentials and trusted integration sessions against customer environments. The company states that the activity did not stem from a flaw in the Salesforce platform and that affected customers were notified directly. The observed behavior included using Salesforce as a relay through Apex and abused Named Credentials, inspecting existing Apex and integration settings before deploying custom Apex, REST endpoints and Visualforce components, and testing the compromised account’s effective permissions by enumerating users, profiles and Permission Sets. The attackers kept retrying code-execution and integration paths, including anonymous Apex, and audit logs showed rapid, dynamic automation that Salesforce reads as an agentic-like operator.

The recommended defenses are phishing-resistant MFA for all users, with Salesforce already enforcing it for admins and MFA for all users, User Email Domain Restrictions, short-lived context-bound OAuth tokens, and step-up authentication for sensitive actions such as bulk export and permission changes. Also recommended are IP allowlisting for users and Connected Apps, behavioral detection of full attack sequences, Event Monitoring streamed to a SIEM, regular scanning of repositories for exposed secrets, and a response plan able to disable an integration, revoke tokens and reset credentials within hours.

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

Worth reading?

Must-readAgentforce and AI

How HXL widgets reach the screen in Agentforce and MCP clients (opens in a new tab)

You will learn the two routes a Headless Experience Layer widget takes from a user's question to a card on screen, one through Agentforce and one through MCP clients, and where each route fails.

Why read this

You will also see how to troubleshoot a missing card in each.

Route 1: Agentforce

  • LLM calls show_tool_results
  • LLM sees result plus ID only
  • Agentforce Client draws with Lightning Web Components

Route 2: MCP clients

  • Host shows any tool with a renderer
  • LLM sees data, never the widget
  • Renderer draws in a sandboxed iframe
The two routes differ in who decides to show the card and who draws it

The Headless Experience Layer beta lets a developer define a widget once and show it as an interactive card in Agentforce, Slackbot, Claude and ChatGPT. How the widget appears depends on the client the user is chatting in, and the article splits this into two runtime routes. The example throughout is a customerReviews widget from the Pronto sample app, which an agent produces by calling the getCustomerReviews Apex action.

In Route 1, inside Agentforce, the runtime stores the action’s output under a short ID and marks it as displayable when the surface supports widgets and the action is flagged is_displayable. The LLM then calls the built-in show_tool_results action with that ID, which carries only a caption and the ID. The runtime resolves the result and its Custom Lightning Type, and the Agentforce Conversation Client hydrates the widget in the browser from JSON. Rendering depends on the model choosing to make that call, so the article suggests asking for the card in the agent’s instructions.

In Route 2, an MCP server advertises a renderer address for each tool. The client loads the HXL renderer in a sandboxed iframe and calls the tool, and the server returns text for the model, the raw structured output, and a hydrated widget in metadata. The host pushes the widget into the iframe, while the LLM reads only the data and writes the answer.

The article closes with a comparison of the two routes on who decides to show the card, what the LLM sees, where data meets the widget and who draws it. It also gives a troubleshooting checklist for each route, including checking for the is_displayable flag, the show_tool_results call, the resource URI in tools/list, and whether the tool call returned an error.

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

Worth reading?

RecommendedAgentforce and AI

AIforce exposes Salesforce configuration to outside agents through MCP and the Headless Toolkit (opens in a new tab)

You will learn what AIforce and the Headless Toolkit expose from your org, the five tools that make it up, and how the security model applies to agents acting as users.

Why read this

You will also see what admins should review before opening the org to external agents.

Headless Toolkit

  • MCP servers
  • APIs
  • Skills
  • Plugins
  • Developer tools
The Headless Toolkit has five parts that expose org configuration outward

Salesforce’s AIforce strategy lets people work with Salesforce from the tools they already use, such as Slack, Claude and other AI clients, rather than only from the Salesforce UI. The article places AIforce as the interface layer above Data 360, Customer 360 and Agentforce. It stresses that the Lightning UI, Reports and Dashboards are not going away.

The Headless Toolkit, formerly called Headless 360, is the set of technologies that makes this work. It has five parts: MCP servers, which use OAuth and may be Salesforce-hosted or custom; APIs, including the Agent API and the platform data APIs; skills, which are instruction folders that AI clients load for a task; plugins, which package skills with commands and MCP connections; and developer tools such as the Salesforce CLI, Agentforce Vibes and the declarative Agent Script format. The article says this is an umbrella over existing capabilities rather than a new product, citing 60+ MCP tools, 4,000+ APIs and 220+ CLI commands.

For developers building external applications, there are two routes: the Headless Experience Layer, which renders workflows natively in channels such as Slack, WhatsApp, voice or mobile, or direct calls to the APIs and MCP tools with a custom UI. Either way, the flows, data models and guardrails configured in the org are what they build on.

On security, the article says Sharing Rules, field-level security and Permission Sets are respected however data is accessed, and that calls pass through the Trust Layer. Every call carries identity, access, capability and governance controls, so Validation Rules, triggers and governor limits still apply. Because an agent can do anything the acting user can do, the article advises reviewing profiles and Permission Sets before exposing the org. Agentic Identity, where agents have their own permissions and credentials, is described as planned for the near future.

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

Worth reading?

RecommendedAgentforce and AI

Builder Central lets admins build and edit in a virtual layer before touching the sandbox (opens in a new tab)

You will learn how Builder Central keeps proposed metadata changes out of your sandbox until you approve them, how it edits existing flows and apps, and what its new project-plan review step does.

Why read this

The piece is a podcast transcript, so the specifics are mostly the speakers' claims and a demo.

  1. Describe the idea in Builder Central
  2. Review the project plan before building
  3. Explore changes in the virtual environment
  4. Publish to the sandbox on your approval
How a Builder Central change reaches the sandbox, as described in the episode

Builder Central, now in beta, is a Salesforce tool that lets admins go from a description of an idea to a working solution on the platform without writing code. The podcast hosts describe it as the result of about two and a half years of internal work, built on the team’s headless and MCP efforts, and aimed at low-code builders. Early customers reported that tasks which took seven to ten days for several people now take one person two to three hours.

The central design point is that Builder Central works in a virtual environment rather than changing sandbox metadata while you build. Changes stay out of the org until you explicitly publish the project to the sandbox with a button or by asking the agent to do it. Visualizers show flows and other output as they would look in the org before anything is deployed, and the speakers say the team keeps adding them.

The tool also covers the maintenance work that makes up most of an admin’s job. Because it can read all the metadata in an org, it can refactor or test existing flows, and the hosts say it generated flow tests that a product manager judged to be good. A feature due around TDX will let users pull an existing app into a project and restyle it with a brand kit. A new step, rolling out that week, has the agent build a project plan for the user to review and approve before it starts building, and inline editing lets users select a single component to change.

The episode is promotional in tone and mostly anecdotal, so treat the productivity figures and comparisons with Claude Code as the speakers’ own account. The practical takeaway is the publish-on-approval workflow and the plan review step, which are the parts most relevant to governance and sandbox risk.

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

Worth reading?

RecommendedFlow and admin

Finding Contacts with a blank AccountId after a Salesforce migration (opens in a new tab)

You will know how to find Contacts with no Account using SOQL or a report, why such Contacts are private by default, and how to triage them before attaching any of them to an Account.

  1. Query Contacts where AccountId is null
  2. Compare count with source system
  3. Label each row attach, private or investigate
  4. Attach only reviewed Attach rows
  5. Re-run null query and spot-check
Triage steps for orphan Contacts after a load

After a migration, a Contact can keep all its field values and still have a blank AccountId. That is an orphan, which differs from a wrong-parent Contact whose AccountId points at the wrong company. The article notes that Salesforce Help says Contacts not linked to an Account are private, visible only to the owner and to administrators with View All Data or Modify All Data, and not governed by Contact Sharing Rules. It lists example causes such as Accounts loaded after Contacts or a failed parent lookup on insert, while stressing that a blank AccountId is one finding to be assessed rather than a diagnosis.

The query is a SOQL statement filtering on AccountId = null, optionally combined with an External ID field to narrow to migration-loaded records, and a count can be compared with the source system’s count of Contacts without an account. The same set can be produced from a Data Loader export or a standard report. The author recommends a triage step that labels each row as attach, leave private or investigate, never attaching the whole list automatically, matching on Contact Id, and re-running the null query after updates.

The piece closes with its limits: intentional private Contacts are normal, a null check cannot detect a wrong parent, and users without View All Data may under-count what they can see. It also promotes a paid CSV comparison tool for wrong-parent checks.

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

Worth reading?

Flow and admin

Fixing common Salesforce Import errors and the surprises that follow a Load (opens in a new tab)

You will learn how to choose between the Data Import Wizard and Data Loader, what the most common import error messages mean and how to fix them, and why duplicate-rule matches and skipped automation can make a successful import look wrong.

Data Import Wizard

  • Runs in the browser from Setup
  • Up to 50,000 records per load
  • Objects the wizard lists in Setup
  • Results in Recent Import Jobs

Data Loader

  • Desktop app, Java 17 or later
  • Up to 150 million with Bulk API 2.0
  • All objects, including Custom Objects
  • Success and error CSV files per run
The Data Import Wizard and Data Loader differ in where they run and how far they scale

The article starts by separating the two import routes. The Data Import Wizard runs in the browser from Setup, suits smaller loads under 50,000 records on supported objects, and is the easier starting point. Data Loader is a desktop application that needs Java 17 or later, covers all objects including Custom Objects, supports upserts, deletes and scheduled command-line loads, and is the route to take when a file outgrows the wizard.

Most failures come from the file rather than the tool. The article walks through the usual causes: a missing required field such as Last Name, values that do not match a picklist exactly, inconsistent date formats, and values longer than the field allows. It explains that duplicate errors can fire against existing Contacts or Accounts because standard matching rules compare names and contact details by similarity, so the record to update may already exist under another Record Type. It also notes that automation can be skipped unless the trigger-workflow option is ticked, and that existing triggers or Validation Rules can reject mixed batches, which a split-by-value approach can work around. Import jobs run from a queue, so admins check Recent Import Jobs and Bulk Data Load Jobs for status and failure reasons, and users should check List Views, ownership and failed rows before re-importing.

The piece also covers fields missing from the mapping list because of page layout or field-level security, the permission needed to import Custom Objects, and the limits of imports, which cannot merge existing duplicates or change matching rules. The closing sections promote the author’s own tools, which the reader should weigh accordingly.

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

Worth reading?

Agentforce and AI

Keep approval policy in data and deterministic code, not in an agent's prompt (opens in a new tab)

You will see why an AI agent should not decide business rules like discount approval, and how to structure it with an explicit approval matrix, gated tools, and a needs_human outcome.

Why read this

The code is generic Python rather than Salesforce-specific.

  1. Agent calls request_discount
  2. Look up approver in matrix
  3. Approver found: pending approval
  4. None available: needs human
How a discount request is routed through the approval gate

The article argues that an AI agent is essentially an LLM in a loop, and that the difficulty in a company lies in the policy questions nobody has answered, such as who may approve a discount above a rep’s limit when the usual approver is unavailable. An agent should not invent such a policy, because any answer it gives looks like a decision but is only a guess.

The proposed design moves policy into data the business owns, such as a table or Custom Metadata listing discount thresholds, the role allowed to approve, and a backup role. A deterministic function looks up the approver and returns nothing when nobody is available, so the case escalates instead of being guessed. Tools that change money, prices or contracts never apply changes directly; they return a pending proposal that a gate handles.

The loop itself stays simple, but it needs a step limit, an allowlist of registered tools, and a first-class needs_human result that explains why the agent stopped. Read and write tools should be treated differently. The author also notes that decisions expressible as simple rules belong in Flow, Apex or plain code, and that agents suit cases needing interpretation of free text or messy context.

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

Worth reading?

Agentforce and AI

Agentforce Coworker is switched on in some orgs, so check it before users ask (opens in a new tab)

The reader will learn what Agentforce Coworker does, how to find out whether it is already enabled in their org, and why sharing and permissions should be reviewed before rollout.

  1. Check whether Coworker is already on
  2. Review sharing and fix over-broad access
  3. Build a few focused agents
  4. Tell users what Coworker can do
A suggested order for rolling out Agentforce Coworker in an org

Agentforce Coworker is described as Salesforce’s AI assistant for employees, sitting in the search bar and routing user requests to specialist agents. Without well-built agents it can still answer questions from org data but can do little else. The article says it reached general availability at Dreamforce and that more than 185,000 people use it.

The article notes that from August 10, 2026, Salesforce automatically turned on Coworker for customers with unmetered user-based AI seats, which can be checked under Setup, Agentforce Coworker. HIPAA, health and life sciences, and government orgs were not auto-enabled, and Coworker is not covered by the HIPAA Business Associate Addendum. Pricing is said to depend on contract terms.

The main warning is that Coworker respects each user’s existing permissions and Sharing Rules, so it will surface any over-broad access quickly. The suggested rollout is to check the enablement setting, review sharing first, build a few focused agents for common requests such as renewal risk and case status, and tell users what the assistant can and cannot do.

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

Worth reading?

DevOps

Measure AI's effect on Salesforce delivery with DORA metrics, not output counts (opens in a new tab)

You will learn why output measures such as tickets closed and pull requests merged can mislead when judging AI-assisted development, and which DORA metrics, including the newer rework rate, show whether AI is saving time.

Why read this

The article also covers the human signals to watch alongside them.

  1. Deployment frequency
  2. Lead time to change
  3. Change failure rate
  4. Time to recover
  5. Rework rate
The four DORA metrics plus rework rate, used together to test whether faster delivery costs stability

The article argues that organisations judge AI-assisted development by activity such as lines of code, tickets closed and pull requests merged, which are easy to game and say little about whether the work is valuable. It cites Google’s DORA research finding that rising AI use correlates with greater org instability, and that the rework this creates can consume the time AI was meant to save.

The author recommends returning to the four DORA metrics: deployment frequency, lead time to change, change failure rate and time to recover, together with the rework rate metric DORA added in 2024. Taken together, these show whether faster delivery is coming at the cost of stability. The author also stresses that the numbers show what is happening but not why, so teams should track human signals such as trust in AI output, verification load and user adoption.

The piece closes with a promotional section for Gearset’s AI agent Cam and its DevOps performance dashboard, which tracks DORA metrics from a pipeline. The promotional content is brief and the general guidance stands apart from it.

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

Worth reading?