How to
How to connect Claude to Salesforce with write access
The Salesforce connections most teams try first can query records and pull reports, but the writing stops there. A custom MCP connector is how Claude actually moves your pipeline.
Connect Claude to Salesforce through a custom MCP connector that authenticates as your own Salesforce user with OAuth 2.0. Claude can then update opportunity stages and amounts, log calls and emails as activities, and create leads and contacts. Read and write tools are separate, and destructive actions wait for your approval.
Key takeaways
- Available Salesforce connections tend to be read-leaning: querying records and pulling reports works, but updates are limited or unavailable.
- A custom connector adds write tools, so Claude can update opportunity stages, log activities, and create leads and contacts.
- The connector authenticates as your Salesforce user and inherits your profiles and sharing rules, never more.
- Destructive actions like delete are gated behind a confirmation you approve every time.
Can Claude read and update Salesforce records?
Claude can read Salesforce records through most existing connections, but updating them is the gap. Today's options are often read-leaning or cover a thin slice: querying and reporting work, while editing fields, logging activities, and moving opportunities are limited or unavailable. A custom connector adds those write actions with scoped controls.
Reading was never the hard part. Claude can usually query accounts, contacts, leads, opportunities, and cases, and pull reports. The problem shows up the moment you ask it to act on what it found. Update this stage. Log that call. Create the lead. That is where read-leaning connections run out.
A custom MCP connector closes the gap with dedicated write tools. Claude can update_opportunity to change a stage, amount, or close date, log_activity to record a call or meeting on the right account, and create_lead or create_contact linked to the correct account.
How do I connect Claude to Salesforce with write access?
You connect Claude to Salesforce by having a custom MCP server built that authenticates with OAuth 2.0 using the narrowest scopes the work needs. Once connected, Claude reads and writes as your own Salesforce user, with read and write tools separated and hard-to-reverse actions gated behind your confirmation.
The setup is done for you, not by you:
- 1Tell us what your team needs Claude to do in Salesforce, for example move opportunities, log activities, or keep account fields current.
- 2We build a small MCP server with read tools (query records, pull reports) and write tools (update fields, log activities, create records) kept separate.
- 3You authenticate through OAuth 2.0 as your own Salesforce user, so Claude inherits your existing permissions, profiles, and sharing rules.
- 4Claude starts acting on records in conversation, with destructive actions like delete requiring your confirmation before they run.
Because the connector authenticates as your user, there is no service account with god-mode access sitting in your org. Claude can only reach the records your own login can reach.
What Salesforce pipeline work can Claude do for me?
With full read-write access, Claude handles the CRM hygiene that used to mean manual data entry. It updates an opportunity's stage, amount, or close date as the deal progresses, logs calls and emails as activities, creates leads and contacts, and keeps account fields current, all where the record already lives.
Typical pipeline work a custom Salesforce connector covers:
- Update an opportunity's stage, amount, or close date as a deal progresses.
- Log a call, email, or meeting as an activity on the right account or contact.
- Create a new lead or contact and link it to the right account.
- Create or update a case and route it to the right queue.
- Find records matching a query and propose batched field updates.
The batched-update case matters most for hygiene. Claude can find every record matching a query, show you the proposed changes, and apply them once you approve, instead of you clicking through records one by one.
Is it safe to give Claude write access to Salesforce?
Yes, when the connector is scoped correctly. It authenticates as your user through OAuth and inherits your permissions, profiles, and sharing rules, so Claude can never see or change data your own account cannot. Read and write tools are separate, and deletes only run after you approve them.
Routine updates and activity logging can flow freely while the riskier actions stay deliberate. You decide where that line sits for your team.
Deletes are always gated
Destructive actions like delete are separate write tools that only run after you confirm them. Claude can prepare the change and show you exactly what it will edit, but nothing irreversible happens without your sign-off.
Why not just use an off-the-shelf Salesforce integration?
Off-the-shelf Salesforce connections are fine if reading is all you need. They query records and pull reports well. The limits appear when you want Claude to update fields, log activities, and move deals reliably, with your own approval flow. A purpose-built connector is scoped to exactly that work.
The honest framing: existing options are not broken, they are thin. If your team's actual request is 'Claude, move this deal to Negotiation and log the call,' a read-leaning connection cannot finish the sentence. A custom connector is built around the writes your revenue team actually performs, nothing more.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.