# How to connect LinkedIn public data to Hermes Agent (paste one key, 28 tools) > Connect LinkedIn public data to Hermes 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. Web version: https://claw-link.dev/hermes/linkedin-data Most guides for giving Hermes Agent LinkedIn public data access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical LinkedIn public data setup: pair once in the browser and your always-on Hermes agent can act on LinkedIn public data for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to LinkedIn public data. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect LinkedIn public data** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 linkedin-data # connect LinkedIn public data (browser OAuth) npx -y @useclawlink/cli actions linkedin-data # list available actions npx -y @useclawlink/cli run linkedin-data --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect LinkedIn public data in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your LinkedIn public data account details once. Verify the connection by asking Hermes: > Use LinkedIn public data to linkedindata user profile and walk me through the result in plain English. ### Using a different agent? The Hermes 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 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## LinkedIn public data MCP for Hermes Looking for a LinkedIn public data MCP server for Hermes Agent? ClawLink connects LinkedIn public data to Hermes Agent and exposes 28 LinkedIn public data 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 OpenClaw instead? The [OpenClaw LinkedIn public data integration](https://claw-link.dev/openclaw/linkedin-data) works the same way. ## What the Hermes Agent LinkedIn public data integration can do 28 LinkedIn public data tools are ready for Hermes Agent once the account is connected. ### All 28 LinkedIn public data tools for Hermes | 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 | ## Example prompts **Linkedindata User Profile** > Use LinkedIn public data to linkedindata user profile and walk me through the result in plain English. **Linkedindata User Posts** > Use LinkedIn public data to linkedindata user posts and walk me through the result in plain English. **Linkedindata User Reactions** > Use LinkedIn public data to linkedindata user reactions and walk me through the result in plain English. **Linkedindata User Comments** > Use LinkedIn public data to linkedindata user comments 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use LinkedIn public data Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent LinkedIn public data integration? Yes. ClawLink is the fastest way to connect Hermes to LinkedIn public data: link your LinkedIn public data account once in the browser and Hermes Agent can call the LinkedIn public data API through 28 ready-made tools — no custom code or token handling. ### How do I connect LinkedIn public data to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect LinkedIn public data in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to LinkedIn public data in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want LinkedIn public data working from chat. ### Hermes paired but still can't use LinkedIn public data Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Connect Stack Exchange](https://claw-link.dev/hermes/stack-exchange) — Search and browse questions, answers, and developer knowledge - [Hermes TikTok public data integration](https://claw-link.dev/hermes/tiktok-data) — Read any public TikTok profile, video, comments, hashtag or search. Read-only and not your account: nothing to connect, paid per call from credit - [Connect X (Twitter)](https://claw-link.dev/hermes/twitter) — Post tweets, manage lists, search content, and analyze engagement