# How to connect Salesflare to OpenClaw (paste one key, 63 tools) > Connect Salesflare to OpenClaw with ClawLink: paste your Salesflare key once and 63 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/salesflare The usual route to Salesflare 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 Salesflare setup: install one ClawHub skill, connect Salesflare in the browser, and OpenClaw can call real Salesflare actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Salesflare. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Salesflare** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 salesflare # connect Salesflare (browser OAuth) npx -y @useclawlink/cli actions salesflare # list available actions npx -y @useclawlink/cli run salesflare --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 Salesflare in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Salesflare API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Salesflare, summarize it in plain English, and point out anything that needs attention. ### 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 Salesflare is connected in the dashboard, that agent calls the same 63 Salesflare 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). ## Salesflare MCP for OpenClaw Looking for a Salesflare MCP server for OpenClaw? ClawLink connects Salesflare to OpenClaw and exposes 63 Salesflare 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 Salesflare integration](https://claw-link.dev/hermes/salesflare) works the same way. ## What the OpenClaw Salesflare integration can do 63 Salesflare 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 63. ### 30 of 63 Salesflare tools for OpenClaw | Tool | What it does | |---|---| | **Get account** `salesflare_get_account` | Get detailed information about a specific account by ID | | **Get AI settings** `salesflare_get_ai_settings` | Retrieve AI settings for the Salesflare team | | **Get contact** `salesflare_get_contact` | Retrieves detailed information for a specific contact by ID | | **Get current user** `salesflare_get_current_user` | Retrieve the details of the currently authenticated user | | **Get custom field** `salesflare_get_custom_field` | Retrieve details of a specific custom field | | **Get meeting** `salesflare_get_meeting` | Retrieve detailed information about a specific meeting by its ID | | **Get opportunity** `salesflare_get_opportunity` | Get detailed information about a specific opportunity by ID | | **Get stage** `salesflare_get_stage` | Get detailed information about a specific pipeline stage by ID | | **Get tag usage** `salesflare_get_tag_usage` | Get tag usage details including workflows, saved filters, and reports | | **Get user** `salesflare_get_user` | Retrieve details of a specific user by their ID | | **Get workflow** `salesflare_get_workflow` | Get detailed information about a specific workflow by ID | | **Get workflow merge fields** `salesflare_get_workflow_merge_fields` | Retrieve available merge fields for workflows in Salesflare | | **List account messages** `salesflare_list_account_messages` | Retrieve a list of messages associated with a specific account in Salesflare | | **List accounts** `salesflare_list_accounts` | List accounts with various filtering options including search, name, creation dates, size | | **List contacts** `salesflare_list_contacts` | List contacts with filtering options | | **List currencies** `salesflare_list_currencies` | Retrieve a list of supported currencies in Salesflare | | **List custom field options** `salesflare_list_custom_field_options` | List available options for a specific custom field in Salesflare | | **List custom field types** `salesflare_list_custom_field_types` | Retrieve a list of available custom field types in Salesflare | | **List custom fields** `salesflare_list_custom_fields` | List custom fields for a specified item class (accounts, contacts, or opportunities) | | **List email datasources** `salesflare_list_email_datasources` | List email data sources | | **List filter fields** `salesflare_list_filter_fields` | List available filter fields for a specific entity type in Salesflare | | **List groups** `salesflare_list_groups` | List groups in Salesflare | | **List my contacts** `salesflare_list_my_contacts` | List contacts belonging to the current user | | **List opportunities** `salesflare_list_opportunities` | List opportunities with extensive filtering options | | **List persons** `salesflare_list_persons` | List persons (non-contact people found in communications) from Salesflare | | **List pipelines** `salesflare_list_pipelines` | List pipelines in the Salesflare system with filtering and sorting options | | **List stages** `salesflare_list_stages` | List pipeline stages in the Salesflare system with filtering and sorting options | | **List tags** `salesflare_list_tags` | List tags in the Salesflare system | | **List tasks** `salesflare_list_tasks` | List tasks with filtering options | | **List users** `salesflare_list_users` | List users (team members) in the Salesflare team | ## Example prompts **Get Account** > Pull the relevant data from Salesflare, summarize it in plain English, and point out anything that needs attention. **Get Ai Settings** > Pull the relevant data from Salesflare, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Salesflare, summarize it in plain English, and point out anything that needs attention. **Get Current User** > Pull the relevant data from Salesflare, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 Salesflare working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Salesflare API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Salesflare account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Salesflare. | 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 Salesflare actions to the runtime in a format your agent can reliably use. | 63 tools for Salesflare are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Salesflare 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 Salesflare in the browser, and the 63 tools above work from chat. There is no SDK and no config file, and the Salesflare key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Salesflare skill but can't call the tools The ClawHub skill teaches OpenClaw about Salesflare, but the calls run through the ClawLink plugin and your connected account. Make sure Salesflare 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 Salesflare 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 Salesflare tools Salesflare 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 Salesflare 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. ### Salesflare 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. ### API key setup works but results look incomplete Double-check that the API key for Salesflare has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Salesflare integration? Yes. ClawLink is the fastest way to connect OpenClaw to Salesflare: link your Salesflare account once in the browser and OpenClaw can call the Salesflare API through 63 ready-made tools — no custom code or token handling. ### How do I add Salesflare to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Salesflare skill from ClawHub, then you click Connect in the dashboard to authorize Salesflare. OpenClaw calls the tools from the next message — no config files, and the Salesflare key you paste is stored server-side instead of in your environment. ### How long does it take to connect Salesflare to OpenClaw? About two minutes. Sign in, click Connect next to Salesflare in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Salesflare up myself? The alternative to ClawLink is usually manual API key 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 Salesflare working from chat. ### OpenClaw installed the Salesflare skill but can't call the tools The ClawHub skill teaches OpenClaw about Salesflare, but the calls run through the ClawLink plugin and your connected account. Make sure Salesflare 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 - [Connect HubSpot](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [OpenClaw CentralStationCRM integration](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Salesforce](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows