C
Cody
OpenClaw Integrations

How to Connect Salesforce to OpenClaw: Setup, Models, and Workflow Guide

·5 min read

If you're searching for "how to connect Salesforce to OpenClaw", the real question is usually not just whether the connection is possible. It's how to make Salesforce usable inside an OpenClaw workflow with the right model, the right context, and the right level of control.

That's the practical framing.

OpenClaw gives you the orchestration layer: connectors, skills, tools, prompts, approvals, and the ability to run workflows where your team already works. Salesforce provides the domain context. The integration becomes valuable when those two pieces are connected cleanly.

What “Connect Salesforce to OpenClaw” Actually Means

In practice, connecting Salesforce to OpenClaw usually involves four layers:

  • Authentication so OpenClaw can securely access Salesforce
  • Tooling or proxy endpoints that expose the right Salesforce actions and data
  • Skills/instructions that tell OpenClaw how to reason over Salesforce context
  • Model selection so the assistant uses the right LLM for the job

That last piece matters more than most people expect.

Which Models Can You Use?

OpenClaw is model-flexible, so a Salesforce integration does not need to be tied to a single provider. Depending on your setup, teams commonly want to use:

  • OpenAI models like GPT-4o, GPT-4.1, and o3 for broad reasoning and tool use
  • Anthropic models like Claude 3.5 Sonnet, Claude Sonnet 4/4.5, and Claude Opus for strong writing, analysis, and long-context work
  • Google models like Gemini 1.5 Pro or newer Gemini models for multimodal and large-context workflows
  • Other model backends if your OpenClaw environment exposes them

The practical point: you can connect Salesforce to OpenClaw once, then run different workflows with different models depending on the job.

For example:

  • Use Claude for nuanced summarisation or drafting
  • Use OpenAI for structured extraction, tool-heavy workflows, or general-purpose copiloting
  • Use Gemini when multimodal or very large context windows matter

A Good Integration Pattern for Salesforce

A strong Salesforce + OpenClaw setup usually looks like this:

  1. OpenClaw receives a request in chat or from an automation
  2. It calls the right Salesforce endpoint or proxy
  3. The selected model reasons over the returned context
  4. OpenClaw returns an answer, draft, classification, or action
  5. High-risk actions stay behind approvals or structured guardrails

That is what makes the setup operational rather than just experimental.

Step-by-Step: Connect Salesforce to OpenClaw

Step 1: Create a Salesforce Connected App

In Salesforce Setup → App Manager → New Connected App. Enable OAuth, add the callback URL for your proxy, and select the OAuth scopes you need (at minimum: api, refresh_token). After saving, note the Consumer Key and Consumer Secret — these are your OAuth credentials.

Step 2: Implement OAuth 2.0 or Use a Named Credential

For a service-to-service integration, the OAuth 2.0 Username-Password flow or JWT Bearer flow is simplest (though the Username-Password flow may be disabled in stricter orgs). Alternatively, Salesforce Named Credentials can manage auth for you. Your proxy needs to handle token refresh — Salesforce tokens expire.

Step 3: Build SOQL Queries and the Proxy

Salesforce's REST API accepts SOQL (Salesforce Object Query Language) via /services/data/v58.0/query?q=SELECT+.... Write a proxy that translates your common queries into SOQL. Write ~/.openclaw/skills/salesforce.md with your key object names, fields, and the SOQL patterns that answer common team questions.

Model-Specific Workflow Ideas

Salesforce + OpenAI

Use this when you want a strong general-purpose setup for extraction, classification, action planning, and tool-driven workflows around Salesforce.

Salesforce + Claude

Use this when you want better writing quality, clearer summaries, stronger nuance, and reliable long-context reasoning over Salesforce data.

Salesforce + Gemini

Use this when the workflow benefits from large context windows, multimodal inputs, or Google-native ecosystem alignment.

Common Mistakes

Most teams do not fail because the model is bad. They fail because:

  • the Salesforce connection is too thin
  • the model lacks the right live context
  • prompts are vague
  • no structured outputs are enforced
  • permissions and approvals are skipped
  • one model is forced to do every job, even when another would be a better fit

The best setup is usually one integration layer, multiple model options, and clear guardrails.

Challenges and Caveats

Governor Limits Are Real

Salesforce enforces governor limits on API calls per day based on your edition and number of licenses. Exceeding them blocks all API access until the limit resets. Design your proxy to cache results and avoid unnecessary calls.

SOQL Is Powerful but Error-Prone

Claude can generate SOQL queries from natural language, but SOQL has specific requirements around relationship queries, subqueries, and aggregate functions. Expect to debug Claude's SOQL output during the initial skill tuning phase.

Sandbox vs Production

Salesforce has separate sandbox and production environments with different OAuth endpoints. Make sure your proxy is configured for the right environment and that you've tested in sandbox before touching production.

Want Salesforce Connected to OpenClaw Without Building the Whole Stack Yourself?

Cody has Salesforce integration built in. Query opportunities, accounts, and forecasts from Slack without Connected Apps, SOQL, or governor limit worries.

Get started with Cody →

Related OpenClaw Guides

Looking for a more workflow-first angle? See: Salesforce AI Automation and Salesforce AI Assistant.

← Back to all guides