How to connect Close to OpenClaw
Connect Close to OpenClaw with ClawLink: paste your Close key once and 39 tools work from chat. No MCP server to run, nothing stored on your machine.

Close is a CRM platform designed to help businesses manage and streamline their sales processes, including calling, email automation, and predictive dialers.. Once connected, OpenClaw can read and act on Close from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Close 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 Close setup: install one ClawHub skill, connect Close in the browser, and OpenClaw can call real Close 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 Close.
- 1
Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin - 2
Connect Close
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Close?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Close in the ClawLink dashboard — paste your Close API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Close, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Close is connected in the dashboard, that agent calls the same 39 Close tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Close MCP for OpenClaw
Looking for a Close MCP server for OpenClaw? ClawLink connects Close to OpenClaw and exposes 39 Close tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Close integration works the same way.
What the OpenClaw Close integration can do
39 Close 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 39.
30 of 39 Close tools for OpenClaw
| Tool | What it does |
|---|---|
Get call close_get_call | Retrieve one Close call activity by ID with optional field projection |
Get contact close_get_contact | Retrieve one Close contact by ID, optionally limiting returned fields |
Get email close_get_email | Retrieve one Close email activity by ID with optional field projection |
Get lead close_get_lead | Retrieve one Close lead by ID with optional field projection |
Get note close_get_note | Retrieves a list of note activities from Close |
Get opportunity close_get_opportunity | Retrieve one Close opportunity by ID with optional field projection |
Get sms close_get_sms | Retrieve one Close SMS activity by ID with optional field projection |
List activities close_list_activities | Lists one page of Close email or call activities using documented filters |
List contacts close_list_contacts | List Close contacts with lead filtering, projection, and offset pagination |
List custom activities close_list_custom_activities | List Close custom activity instances with filters and offset pagination |
List custom activity types close_list_custom_activity_types | Lists the custom activity types defined in a Close organization, returning each type's id and |
List custom object types close_list_custom_object_types | Lists the custom object types defined in a Close organization, returning each type's id and name |
List custom objects close_list_custom_objects | List custom object instances attached to a Close lead, optionally by type |
List events close_list_events | List Close change events with filters, projection, and cursor pagination |
List leads close_list_leads | List or text-search Close leads with field projection and offset pagination |
List opportunities close_list_opportunities | List a page of Close opportunities with offset pagination |
List tasks close_list_tasks | List Close tasks using task, assignee, lead, date, and pagination filters |
Search data close_search_data | Search Close objects using the structured Advanced Filtering query language |
Who am i close_who_am_i | Return the identity (email, name) of the connected Close account |
Create call close_create_call | Creates a new call record in Close.com |
Create email close_create_email | Create or log a Close email activity |
Create lead close_create_lead | Creates a new lead in Close CRM |
Create opportunity close_create_opportunity | Create a Close sales opportunity on an existing lead, or create an Untitled lead for it when |
Create sms close_create_sms | Create an SMS activity on a Close lead to log received, sent, or draft messages, or to send or |
Create task close_create_task | Create a Close task associated with a lead, using task text and an actionable date, with |
Update activity custom field close_update_activity_custom_field | Update mutable settings of one Close activity custom-field definition |
Update custom activity close_update_custom_activity | Update standard and custom fields on one Close custom activity instance |
Update lead custom field close_update_lead_custom_field | Update a Close lead custom-field definition |
Update note close_update_note | Update the mutable content and metadata of one Close note activity |
Update opportunity close_update_opportunity | Update standard and custom fields on one Close opportunity |
Try it: find the Close tool you need
Browse the 30 Close tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Close, 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 Close working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Close API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Close 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 Close. | 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 Close actions to the runtime in a format your agent can reliably use. | 39 tools for Close are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Close 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 Close in the browser, and the 39 tools above work from chat. There is no SDK and no config file, and the Close key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Close skill but can't call the tools
The ClawHub skill teaches OpenClaw about Close, but the calls run through the ClawLink plugin and your connected account. Make sure Close 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 Close 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 Close tools
Close 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 Close 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.
Close 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 Close has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Close integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Close: link your Close account once in the browser and OpenClaw can call the Close API through 39 ready-made tools — no custom code or token handling.
How do I add Close to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Close skill from ClawHub, then you click Connect in the dashboard to authorize Close. OpenClaw calls the tools from the next message — no config files, and the Close key you paste is stored server-side instead of in your environment.
How long does it take to connect Close to OpenClaw?
About two minutes. Sign in, click Connect next to Close in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Close 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 Close working from chat.
OpenClaw installed the Close skill but can't call the tools
The ClawHub skill teaches OpenClaw about Close, but the calls run through the ClawLink plugin and your connected account. Make sure Close 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
OpenClaw SendPulse integration
SendPulse is a multichannel marketing platform for email, SMS, chatbots, CRM, automation, web push, and transactional messaging.
Connect HighLevel Location
HighLevel provides Location-scoped CRM, marketing, conversations, calendars, payments, and business automation APIs.
ActiveCampaign tools
Marketing automation, CRM, and email marketing