How to connect Crustdata to OpenClaw
Connect Crustdata to OpenClaw with ClawLink: paste your Crustdata key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine.
CrustdataAPI KEYMCPCrustData is an AI-powered data intelligence platform that provides real-time company and people data via APIs and webhooks, empowering B2B sales teams, AI SDRs, and investors to act on live signals.. Once connected, OpenClaw can read and act on Crustdata from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Crustdata 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 Crustdata setup: install one ClawHub skill, connect Crustdata in the browser, and OpenClaw can call real Crustdata 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 Crustdata.
1Install 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 Crustdata
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Crustdata?"
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 Crustdata in the ClawLink dashboard — paste your Crustdata API key once.
Verify the connection by asking OpenClaw:
Use Crustdata to enrich person screener and walk me through the result in plain English.
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 Crustdata is connected in the dashboard, that agent calls the same 15 Crustdata tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Crustdata MCP for OpenClaw
Looking for a Crustdata MCP server for OpenClaw? ClawLink connects Crustdata to OpenClaw and exposes 15 Crustdata tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Crustdata integration works the same way.
What the OpenClaw Crustdata integration can do
15 Crustdata tools are ready for OpenClaw once the account is connected.
All 15 Crustdata tools for OpenClaw
| Tool | What it does |
|---|---|
Enrich person screener crustdata_enrich_person_screener | The screener_person_enrich endpoint enriches person data by providing additional information |
Fetch headcount by facet timeseries crustdata_fetch_headcount_by_facet_timeseries | Retrieves headcount data as a timeseries with faceted analysis capabilities |
Fetch investor portfolio data crustdata_fetch_investor_portfolio_data | Retrieves comprehensive investor portfolio data from the Data Lab section of the CrustData API |
Filter decision makers data crustdata_filter_decision_makers_data | Filters and retrieves decision maker data from the CrustData B2B SaaS integration platform |
Post funding milestone time series data crustdata_post_funding_milestone_time_series_data | The FundingMilestoneTimeseries endpoint retrieves time-series data related to funding |
Post headcount timeseries data crustdata_post_headcount_timeseries_data | Retrieves filtered and sorted headcount timeseries data from the CrustData Data Lab |
Post job listings table data crustdata_post_job_listings_table_data | This endpoint retrieves filtered and sorted job listings data for specified company tickers |
Post web traffic data crustdata_post_web_traffic_data | Retrieves filtered and sorted web traffic data from the CrustData platform |
Retrieve linked in posts crustdata_retrieve_linked_in_posts | Retrieves LinkedIn posts for a specified company using CrustData's screener functionality |
Screen metrics and filter conditions crustdata_screen_metrics_and_filter_conditions | The ScreenData endpoint enables advanced data screening and filtering on the CrustData platform |
Screener company information crustdata_screener_company_information | The GetCompanyScreener endpoint allows users to search and filter companies based on various |
Search companies with filters crustdata_search_companies_with_filters | The CompanySearch endpoint enables users to search and filter companies using the CrustData API |
Search for job ID in screener crustdata_search_for_job_id_in_screener | The screener_person_search endpoint allows users to search for persons associated with a |
Search linked in posts by keyword crustdata_search_linked_in_posts_by_keyword | This endpoint enables searching for LinkedIn posts using a specific keyword |
Validate credential crustdata_validate_credential | Validate Crustdata API credentials by testing authentication with a lightweight API call |
Try it: find the Crustdata tool you need
Browse the 15 Crustdata tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Crustdata to enrich person screener and walk me through the result in plain English.
Pull the relevant data from Crustdata, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Crustdata, summarize it in plain English, and point out anything that needs attention.
Use Crustdata to filter decision makers data and walk me through the result in plain English.
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 Crustdata working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Crustdata API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Crustdata 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 Crustdata. | 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 Crustdata actions to the runtime in a format your agent can reliably use. | 15 tools for Crustdata are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Crustdata 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 Crustdata in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Crustdata 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 Crustdata skill but can't call the tools
The ClawHub skill teaches OpenClaw about Crustdata, but the calls run through the ClawLink plugin and your connected account. Make sure Crustdata 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 Crustdata 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 Crustdata tools
Crustdata 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 Crustdata 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.
Crustdata 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 Crustdata 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 Crustdata integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Crustdata: link your Crustdata account once in the browser and OpenClaw can call the Crustdata API through 15 ready-made tools — no custom code or token handling.
How do I add Crustdata to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Crustdata skill from ClawHub, then you click Connect in the dashboard to authorize Crustdata. OpenClaw calls the tools from the next message — no config files, and the Crustdata key you paste is stored server-side instead of in your environment.
How long does it take to connect Crustdata to OpenClaw?
About two minutes. Sign in, click Connect next to Crustdata in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Crustdata 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 Crustdata working from chat.
OpenClaw installed the Crustdata skill but can't call the tools
The ClawHub skill teaches OpenClaw about Crustdata, but the calls run through the ClawLink plugin and your connected account. Make sure Crustdata 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.
