How to connect LinkedIn public data to OpenClaw
Connect LinkedIn public data to OpenClaw with ClawLink: paste your LinkedIn public data key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine.
Read LinkedIn profiles, companies and their employees, posts, comments, reactions, jobs, groups and the Ad Library, and search people and companies. Read-only and not your account: nothing to connect, paid per call from credit. Once connected, OpenClaw can read and act on LinkedIn public data from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to LinkedIn public data 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 LinkedIn public data setup: install one ClawHub skill, connect LinkedIn public data in the browser, and OpenClaw can call real LinkedIn public data 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 LinkedIn public data.
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 LinkedIn public data
Enter your account details in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with LinkedIn public data?"
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 LinkedIn public data in the ClawLink dashboard — enter your LinkedIn public data account details once.
Verify the connection by asking OpenClaw:
Use LinkedIn public data to linkedindata user profile 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 LinkedIn public data is connected in the dashboard, that agent calls the same 28 LinkedIn public data tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
LinkedIn public data MCP for OpenClaw
Looking for a LinkedIn public data MCP server for OpenClaw? ClawLink connects LinkedIn public data to OpenClaw and exposes 28 LinkedIn public data tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes LinkedIn public data integration works the same way.
What the OpenClaw LinkedIn public data integration can do
28 LinkedIn public data tools are ready for OpenClaw once the account is connected.
All 28 LinkedIn public data tools for OpenClaw
| Tool | What it does |
|---|---|
User profile linkedindata_user_profile | A LinkedIn member's profile by URL |
User posts linkedindata_user_posts | A LinkedIn member's recent posts and reposts with reaction and comment counts |
User reactions linkedindata_user_reactions | Posts a LinkedIn member reacted to |
User comments linkedindata_user_comments | Comments a LinkedIn member wrote |
Search people linkedindata_search_people | Search LinkedIn members by name, title, company, school or location |
Search people with email linkedindata_search_people_with_email | Find people with their work email |
Profile from email linkedindata_profile_from_email | The LinkedIn profile that belongs to an email address |
Search services linkedindata_search_services | LinkedIn members who offer a service |
Search locations linkedindata_search_locations | LinkedIn geo ids for a place name, for the geoId filter of the search tools |
Company profile linkedindata_company_profile | Public LinkedIn company page |
Company posts linkedindata_company_posts | Recent public posts of a LinkedIn company page |
Company employees linkedindata_company_employees | Up to 10 people who work at a company, with title, location and profile URL |
Search companies linkedindata_search_companies | Search LinkedIn companies by name, location, size or industry |
Company from domain linkedindata_company_from_domain | The LinkedIn company page for a website domain |
Post detail linkedindata_post_detail | One public LinkedIn post or article by URL |
Post comments linkedindata_post_comments | Comments on a LinkedIn post, up to 100 a page |
Post reactions linkedindata_post_reactions | Who reacted to a LinkedIn post and how |
Comment replies linkedindata_comment_replies | Replies to one LinkedIn comment, by the comment's URL |
Comment reactions linkedindata_comment_reactions | Who reacted to one LinkedIn comment |
Post transcript linkedindata_post_transcript | Transcript of the video in a LinkedIn post |
Search posts linkedindata_search_posts | Search public LinkedIn posts by keyword |
Search jobs linkedindata_search_jobs | Search LinkedIn job listings by title, location, date, experience, workplace, job type and salary, 25 a page |
Job detail linkedindata_job_detail | One LinkedIn job posting |
School profile linkedindata_school_profile | A school's LinkedIn page |
Group detail linkedindata_group_detail | A LinkedIn group |
Search groups linkedindata_search_groups | Search LinkedIn groups by keyword |
Ads search linkedindata_ads_search | Ads in LinkedIn's Ad Library by company or keyword, with country and date filters |
Ad detail linkedindata_ad_detail | One ad from LinkedIn's Ad Library |
Try it: find the LinkedIn public data tool you need
Browse the 28 LinkedIn public data tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use LinkedIn public data to linkedindata user profile and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual integration wiring 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 LinkedIn public data working from chat.
| Manual | ClawLink | |
|---|---|---|
| Setup flow | Collect and store the right LinkedIn public data credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link LinkedIn public data without custom integration screens. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for LinkedIn public data. | 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 LinkedIn public data actions to the runtime in a format your agent can reliably use. | 28 tools for LinkedIn public data are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes LinkedIn public data 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 LinkedIn public data in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the LinkedIn public data 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 LinkedIn public data skill but can't call the tools
The ClawHub skill teaches OpenClaw about LinkedIn public data, but the calls run through the ClawLink plugin and your connected account. Make sure LinkedIn public data 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 LinkedIn public data 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 LinkedIn public data tools
LinkedIn public data 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 LinkedIn public data 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.
LinkedIn public data 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.
The setup form accepts credentials but calls still fail
Re-enter the credentials carefully and verify the account-level permissions for LinkedIn public data. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles.
FAQ
Is there a OpenClaw LinkedIn public data integration?
Yes. ClawLink is the fastest way to connect OpenClaw to LinkedIn public data: link your LinkedIn public data account once in the browser and OpenClaw can call the LinkedIn public data API through 28 ready-made tools — no custom code or token handling.
How do I add LinkedIn public data to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink LinkedIn public data skill from ClawHub, then you click Connect in the dashboard to authorize LinkedIn public data. OpenClaw calls the tools from the next message — no config files, and the LinkedIn public data key you paste is stored server-side instead of in your environment.
How long does it take to connect LinkedIn public data to OpenClaw?
About two minutes. Sign in, click Connect next to LinkedIn public data in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring LinkedIn public data up myself?
The alternative to ClawLink is usually manual integration wiring 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 LinkedIn public data working from chat.
OpenClaw installed the LinkedIn public data skill but can't call the tools
The ClawHub skill teaches OpenClaw about LinkedIn public data, but the calls run through the ClawLink plugin and your connected account. Make sure LinkedIn public data 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
Stack Exchange tools
Search and browse questions, answers, and developer knowledge
TikTok public data tools
Read any public TikTok profile, video, comments, hashtag or search. Read-only and not your account: nothing to connect, paid per call from credit
X (Twitter) tools
Post tweets, manage lists, search content, and analyze engagement