# How to connect Salesforce to OpenClaw (no API keys) > Connect Salesforce to OpenClaw with ClawLink in one click — 179 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/salesforce The usual route to Salesforce access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Salesforce setup: install one ClawHub skill, connect Salesforce in the browser, and OpenClaw can call real Salesforce actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/salesforce ## Setup It takes three steps to connect OpenClaw to Salesforce. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Salesforce** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect salesforce # connect Salesforce (browser OAuth) npx -y @useclawlink/cli actions salesforce # list available actions npx -y @useclawlink/cli run salesforce --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Salesforce in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Salesforce to send email for me and draft the message before sending. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Salesforce is connected in the dashboard, that agent calls the same 179 Salesforce tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Salesforce MCP for OpenClaw Looking for a Salesforce MCP server for OpenClaw? ClawLink connects Salesforce to OpenClaw and exposes 179 Salesforce tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Salesforce integration](https://claw-link.dev/hermes/salesforce) works the same way. ## What the OpenClaw Salesforce integration can do 179 Salesforce tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 179. ### 30 of 179 Salesforce tools for OpenClaw | Tool | What it does | |---|---| | **Send email** `salesforce_send_email` | Send an email through Salesforce | | **Execute sosl search** `salesforce_execute_sosl_search` | Execute a SOSL search to search across multiple Salesforce objects | | **Get a batch of records** `salesforce_get_a_batch_of_records` | Retrieve multiple Salesforce records in a single request with customizable field selection | | **Get account** `salesforce_get_account` | Retrieves a specific account by ID from Salesforce, returning all available fields | | **Get all custom objects** `salesforce_get_all_custom_objects` | Retrieves all Salesforce objects (standard and custom) with detailed metadata | | **Get all fields for object** `salesforce_get_all_fields_for_object` | Retrieves all fields (standard and custom) for a Salesforce object with complete metadata | | **Get all navigation items** `salesforce_get_all_navigation_items` | Gets all navigation items (tabs) that the user has access to | | **Get API** `salesforce_get_api` | Discover available REST API resources for a specified Salesforce API version | | **Get app** `salesforce_get_app` | Get metadata about a specific Salesforce app by ID | | **Get apps** `salesforce_get_apps` | Get metadata for all apps a user has access to | | **Get campaign** `salesforce_get_campaign` | Retrieves a specific campaign by ID from Salesforce, returning all available fields | | **Get chatter resources** `salesforce_get_chatter_resources` | Access Chatter resources directory | | **Get child records** `salesforce_get_child_records` | Get child records for a specified parent record and child relationship name | | **Get compact layouts** `salesforce_get_compact_layouts` | Retrieve compact layout information for multiple Salesforce objects | | **Get composite resources** `salesforce_get_composite_resources` | Retrieve a list of available composite resources in Salesforce | | **Get composite sobjects** `salesforce_get_composite_sobjects` | Retrieves multiple records of the same object type by IDs with a request body | | **Get consent action** `salesforce_get_consent_action` | Retrieve aggregated consent preferences across multiple records for a specific action | | **Get contact** `salesforce_get_contact` | Retrieves a specific contact by ID from Salesforce, returning all available fields | | **Get contact by ID** `salesforce_get_contact_by_id` | Retrieves a Salesforce Contact by its unique ID; the ID must correspond to an existing Contact | | **Get dashboard** `salesforce_get_dashboard` | Gets detailed metadata for a specific dashboard including its components, layout, and filters | | **Get file content** `salesforce_get_file_content` | Returns the binary content of a Salesforce file, including references to external files | | **Get file information** `salesforce_get_file_information` | Retrieve comprehensive metadata and information about a specified file in Salesforce | | **Get file shares** `salesforce_get_file_shares` | Returns information about the objects with which the specified file has been shared | | **Get global actions** `salesforce_get_global_actions` | Retrieve actions displayed in the Salesforce Global Actions menu with metadata | | **Get job failed record results** `salesforce_get_job_failed_record_results` | Retrieve failed records from a Salesforce Bulk API 2.0 ingest job | | **Get job successful record results** `salesforce_get_job_successful_record_results` | Retrieve successfully processed records from a Salesforce Bulk API 2.0 ingest job | | **Get job unprocessed record results** `salesforce_get_job_unprocessed_record_results` | Retrieve unprocessed records from a Salesforce Bulk API 2.0 ingest job | | **Get last selected app** `salesforce_get_last_selected_app` | Retrieves the app the current user last selected or the app the user sees by default | | **Get lead** `salesforce_get_lead` | Retrieves a specific lead by ID from Salesforce, returning all available fields | | **Get list view actions** `salesforce_get_list_view_actions` | Retrieve header actions on list views | ## Example prompts **Send Email** > Use Salesforce to send email for me and draft the message before sending. **Execute Sosl Search** > Search Salesforce for what I need, summarize the results, and tell me the next best action. **Get A Batch Of Records** > Pull the relevant data from Salesforce, summarize it in plain English, and point out anything that needs attention. **Get Account** > Pull the relevant data from Salesforce, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Salesforce working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Salesforce app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Salesforce through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Salesforce. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Salesforce actions to the runtime in a format your agent can reliably use. | 179 tools for Salesforce are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Salesforce to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Salesforce in the browser, and the 179 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Salesforce skill but can't call the tools The ClawHub skill teaches OpenClaw about Salesforce, but the calls run through the ClawLink plugin and your connected account. Make sure Salesforce is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Salesforce from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Salesforce tools Salesforce tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Salesforce call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Salesforce returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Salesforce and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Salesforce integration? Yes. ClawLink is the fastest way to connect OpenClaw to Salesforce: link your Salesforce account once in the browser and OpenClaw can call the Salesforce API through 179 ready-made tools — no custom code or token handling. ### How do I add Salesforce to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Salesforce skill from ClawHub, then you click Connect in the dashboard to authorize Salesforce. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Salesforce to OpenClaw? About two minutes. Sign in, click Connect next to Salesforce in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Salesforce up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Salesforce working from chat. ### OpenClaw installed the Salesforce skill but can't call the tools The ClawHub skill teaches OpenClaw about Salesforce, but the calls run through the ClawLink plugin and your connected account. Make sure Salesforce is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [HubSpot](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM tools](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [OpenClaw RepairShopr integration](https://claw-link.dev/openclaw/repairshopr) — RepairShopr is a comprehensive repair shop management software designed to streamline operations, manage customer relationships, and enhance business efficiency.