Claude Is Connected to Salesforce. Here's What to Actually Ask It.

You followed the setup guide. You registered the External Client App, got the OAuth scopes right on the first try or the third, and Claude now has a live connection into your Salesforce org.

Then you type "hi" into the chat box and stare at it.

That moment happens to almost everyone who finishes a new integration. The setup gets all the attention. What to actually do with it gets none. Here are six things worth asking Claude once Claudeforce is live in your org. Not toy examples. The kind of work that normally eats an admin's afternoon.

1. Explain a schema you didn't build

Inherited orgs are the norm, not the exception. Someone configured half these fields three admins ago, and nobody left notes. Instead of clicking through Setup one field at a time, ask Claude to walk the object for you.

"Walk me through every field on the Opportunity object and tell me which ones actually block a deal from closing."

2. Ask for the report you never had time to build

Every admin has a backlog of one-off requests that never quite justify a saved report. Claude can run that query on the spot instead of you adding it to a list.

"Which accounts have an open case older than 30 days with no activity logged in the last two weeks?"

3. Run a data hygiene sweep

Duplicate leads, orphaned records, required fields nobody actually enforced. Every org accumulates this quietly, and cleaning it up is nobody's job until it's everybody's problem. Point Claude at it directly.

"Find Contacts with no Account, no Email, and no logged activity in the last twelve months."

4. Get a plain-English read on automation someone else wrote

This is the one small teams feel the most. You're the only admin, you inherited a Flow or an Apex trigger with zero documentation, and touching it feels like a bet. Ask Claude to read it first.

"Read this Apex trigger and tell me exactly what happens when an Opportunity moves to Closed Won."

5. Pull cross-object context without fifteen open tabs

Instead of clicking Account, then Contacts, then Cases, then Opportunities, and holding it all in your head, let Claude assemble the picture.

"Summarize everything that's happened on the Acme Corp account this quarter: cases, opportunities, and contact activity."

‍

6. Sanity-check a change before you make it

The classic surprise is deleting a field and finding out three Flows depended on it. Ask first.

"What Flows, Validation Rules, or Apex reference the Discount_Percent field, before I remove it?"

The catch: Claude only knows what you're allowed to know

All of this works because Claude is authenticated as a real Salesforce user through OAuth. That's also the limit. Whatever profile and permission set that user has, Claude has. Nothing more.

On a small team, this gets specific fast. If you and your co-admin each connect Claude under your own login, you can get two different answers to the same question, depending on what your permission sets allow. And when Claude executes a write action, it lands in the audit trail as whatever user authorized the connection. Not as "Claude." Someone asking six months from now why a record changed is going to get an answer that leaves that part out.

That's a governance question, not a should-you-use-this question, and it deserves its own post. For now: know that the account you connect controls what you get, and treat write actions with the same caution you'd give any other integration with production access.

‍

FAQ

What is Claudeforce?

The expanded partnership between Salesforce and Anthropic that connects Claude to Salesforce data, workflows, and governed actions. It covers a few different pieces, including Claude running inside Salesforce and Salesforce data reaching Claude through Hosted MCP Servers.

How do I connect Claude to my Salesforce org?

Through an External Client App, a couple of specific OAuth scopes, and a callback URL that has to match exactly. It's a short setup with a few steps that are easy to get wrong on the first try. We wrote a full walkthrough here: How to Connect Claude to Salesforce with Claudeforce.

Can Claude actually change records, or just read them?

Both, depending on the OAuth scopes and the permissions of the account you connect. Hosted MCP Servers support running SOQL queries, modifying records, and executing actions. What Claude can touch is bounded by whatever that connected user is allowed to touch.

Is Claudeforce the same as Agentforce?

No. Agentforce is Salesforce's own agent platform, running inside Salesforce. Claudeforce is the partnership that brings governed Salesforce context into Claude, and brings Claude into Salesforce as a reasoning model. Related work, different products.

Should I worry about what Claude can see?

The same way you'd worry about any integration with API access to your org. Claude only sees what the connected user's profile and permission sets allow, nothing more.

Is this safe to use in production?

Salesforce still lists Hosted MCP Servers as Beta. Treat production access the way you'd treat any beta integration: start read-heavy, keep write actions scoped and reviewed, and expect the setup process to keep changing.

Claude connected to Salesforce is a genuinely useful research and documentation tool once you get past the blank chat box. Just remember that everything it touches is still your org, your data, and your responsibility to track.

That tracking problem, knowing what changed, when, and by whom, isn't unique to AI tools. It's the same problem Blue Canvas exists to solve for every other kind of Salesforce change. Claude just adds one more source of changes worth keeping an eye on.