rokan.

How do I connect an AI agent to Salesforce in 2026?

Have the customer’s Salesforce admin install an External Client App, then connect over OAuth 2.0 as an API-only integration user whose permission set covers exactly the objects and fields the agent reads and writes. Since Spring ’26, new connected apps can’t be created by default, and since September 2025 users can’t authorize a connected app the org hasn’t installed without a specific permission.

Updated · Sources linked inline

What changed

  • August 2025. Attackers used OAuth tokens stolen from Salesloft Drift, an AI chat vendor, to export data from customers’ Salesforce orgs; reports put it at more than 700 orgs (Google Threat Intelligence). Security teams now look hard at any AI vendor that asks for OAuth into their CRM.
  • September 2025. Users can’t authorize a connected app the org hasn’t installed unless they hold the “Approve Uninstalled Connected Apps” permission (Salesforce docs).
  • Spring ’26. New connected apps can’t be created by default. Build new integrations as External Client Apps.

Step by step

  1. Write the access request first. List every object and field the agent reads or writes, and why. The admin builds the permission set from this list, and security reviews it.
  2. The admin installs your External Client App in the customer’s org, with the OAuth scopes the agent needs and nothing broader.
  3. Create an API-only integration user. The Integration User license starts with no object access, and a field without field-level security is silently missing from results, with no error (Salesforce Help). Read back every field in the sandbox to prove it’s visible. Enterprise and Unlimited orgs include 5 free API-only Integration User licenses (Gearset (blog, confirm)).
  4. Test writes in a sandbox with the org’s automation on. Validation rules, required fields, flows and Apex triggers run on API writes and can reject or change them, even when the same edit works in the UI. Confirm when the Full sandbox was last refreshed; one guide puts the limits at every 29 days for Full, 5 for Partial Copy and 1 for Developer (Xappex (blog, confirm)).
  5. Budget API calls. The daily API request limit is org-wide and shared with every other integration; on Enterprise Edition it is 100,000 plus 1,000 per license over a rolling 24 hours (Salesforce limits). Size the agent’s calls from past volume, cache reads, and stay well under the pool so the customer’s other jobs don’t fail. Professional Edition needs API access added.
  6. Give security a revoke plan: short-lived, scoped tokens kept in the customer’s vault, IP restrictions where possible, and a revoke-all procedure you have actually run.

The message to send the admin on day 1

Copy, then fill in the brackets

Hi [name], to connect [agent] to Salesforce we need three things: (1) our External Client App installed in your org with the scopes listed below, (2) an API-only integration user with a permission set for exactly these objects and fields: [list], and (3) access to a sandbox, plus the date it was last refreshed. Tokens stay short-lived in your vault, and we can revoke all of them in one step.

What breaks after launch

  • Automation added later. An admin adds a flow and the agent’s writes start failing or fanning out. Rerun the replay suite whenever the org’s automation changes.
  • Missed events. Change Data Capture and other streamed events are kept for 72 hours. Track replay IDs and reconcile after any outage (Salesforce docs).
  • Encrypted lookups. Shield’s probabilistic encryption blocks filtering on encrypted fields such as phone, which breaks caller lookup (Avochato help (blog, confirm)). Check for encrypted fields when you connect.
  • Prompt injection through web forms. If the customer also runs Agentforce, the ForcedLeak bug (CVSS 9.4, patched September 2025) let text submitted through Web-to-Lead send CRM data to an expired allowlisted domain (The Hacker News (news report, confirm)). Check that every allowlisted domain is still owned.

Short answers

Can I still create a connected app for a new Salesforce integration?

Not by default. Since Spring ’26, new connected apps can’t be created by default, so build new integrations as External Client Apps installed by the customer’s Salesforce admin.

Which Salesforce user should an AI agent connect as?

An API-only integration user with a permission set for the exact objects and fields the agent needs. It starts with no object access, and a field without field-level security silently drops out of results.

Will an AI agent use up the customer’s Salesforce API limit?

It can. The daily API request limit is shared across every integration in the org, so size the agent’s calls from past volume, cache reads and stay well under the pool.