Skip to content
FidelicRoster →

Salesforce integration · OAuth + REST

Connect AI agents to your Salesforce org

AI agents that read your Salesforce accounts, opportunities, and activities, draft new records, and post the result to Slack — pipeline briefs, account prep, QBR docs, and CRM hygiene.

How a Fidelic agent reaches Salesforce.

The connection

What's wired

Fidelic agents connect to Salesforce through OAuth + the Salesforce REST and Bulk APIs. Your agent reads the objects the org admin explicitly grants it — Accounts, Opportunities, Contacts, Activities — with scopes you control.

When the agent reads, it stays inside the objects you've shared. Nothing leaves your Salesforce org unless the agent posts the result to Slack or writes a Note or Task into a record you authorized.

→ Salesforce official API docs

Set it up

How to connect

Before you start

  • A Salesforce org on any edition — Essentials, Professional, Enterprise, or Unlimited.
  • Org admin or a System Administrator who can install Connected Apps.
  • A Slack workspace where the agent will live and post.
  • A decision on which Salesforce objects the agent should reach.
  • About five minutes for the OAuth flow plus a thirty-minute background index build.

The steps

  1. Sign in to Fidelic and pick the agent. From the Roster, choose the agent that needs Salesforce access. Each agent has a Salesforce connect button on its setup screen.
  2. Authorize Salesforce. Click Connect Salesforce. The OAuth dialog opens; sign in with your org admin account. The app appears in Setup → Apps → Connected Apps under the name Fidelic — [agent codename].
  3. Pick the objects the agent should reach. Salesforce shows a permissions screen. Select the standard and custom objects the agent will read or write to. You can change this any time from Setup → Connected Apps.
  4. Confirm and finish. The agent runs a test read against the first object. When it passes, your Slack channel shows a Connected to Salesforce message naming the agent.
  5. Try the first agent action. Ask the agent for an account brief in Slack — it surfaces the answer with citations to specific Salesforce records.

The edges

Connection limits

Where the connection draws the line:

  • · The agent reads only objects the admin explicitly granted. It does not auto-discover new objects.
  • · Salesforce flows and triggers are out of scope; the agent reads their output, not the flow definitions.
  • · Bulk reads above 100,000 records per day require a Bulk API license you arrange separately.

The path

Where the data goes

The connection runs inside your sandboxed Anthropic project. One project key per Fidelic customer; Fidelic infrastructure does not see your platform data.

Anything the agent reads stays inside your environment. The only data that leaves is what the agent posts to Slack or writes back to a destination you authorized — and you can revoke either at any time from the platform's connections panel.

→ Read the full security architecture

Where to next