# How to connect LinkedIn to Grok Bot (no API keys) > Connect LinkedIn to Grok Bot with ClawLink in one click — 10 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/linkedin Grok Bot runs on its own cloud computer, so most LinkedIn guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical LinkedIn setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real LinkedIn actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect linkedin` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to LinkedIn. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect LinkedIn** — `npx -y @useclawlink/cli connect linkedin`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect linkedin # connect LinkedIn (browser OAuth) npx -y @useclawlink/cli actions linkedin # list available actions npx -y @useclawlink/cli run linkedin --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect linkedin ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Create it in LinkedIn for me, then confirm the important fields before you finish. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once LinkedIn is connected in the dashboard, that agent calls the same 10 LinkedIn 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 MCP for Grok Bot Looking for a LinkedIn MCP server for Grok Bot? ClawLink connects LinkedIn to Grok Bot and exposes 10 LinkedIn 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 a different agent? The [OpenClaw LinkedIn integration](https://claw-link.dev/openclaw/linkedin) and the [Hermes LinkedIn integration](https://claw-link.dev/hermes/linkedin) connect the same ClawLink account the same way. ## What the Grok Bot LinkedIn integration can do 10 LinkedIn tools are ready for Grok Bot once the account is connected. The 8 below are the ones people reach for most; your agent can call all 10. ### 8 of 10 LinkedIn tools for Grok Bot | Tool | What it does | |---|---| | **Create comment on post** `linkedin_create_comment_on_post` | Comment on a LinkedIn post | | **Create linked in post** `linkedin_create_linked_in_post` | Publish a post on LinkedIn | | **Get ad targeting facets** `linkedin_get_ad_targeting_facets` | Get LinkedIn ad targeting facets | | **Get images** `linkedin_get_images` | Get images from a LinkedIn post | | **Get my info** `linkedin_get_my_info` | Get the authenticated LinkedIn member profile | | **Search ad targeting entities** `linkedin_search_ad_targeting_entities` | Search LinkedIn ad targeting entities | | **Get image** `linkedin_get_image` | Retrieve details of a LinkedIn image using its URN | | **Create article or URL share** `linkedin_create_article_or_url_share` | Create an article or URL share on LinkedIn using the UGC Posts API | ## Example prompts **Create Comment On Post** > Create it in LinkedIn for me, then confirm the important fields before you finish. **Create Linked In Post** > Create it in LinkedIn for me, then confirm the important fields before you finish. **Get Ad Targeting Facets** > Pull the relevant data from LinkedIn, summarize it in plain English, and point out anything that needs attention. **Get Images** > Pull the relevant data from LinkedIn, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want LinkedIn working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a LinkedIn app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect LinkedIn through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for LinkedIn. | 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 actions to the runtime in a format your agent can reliably use. | 10 tools for LinkedIn are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes LinkedIn 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 Grok Bot users instead. You install the plugin once, connect LinkedIn in the browser, and the 10 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect LinkedIn 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 tools LinkedIn 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 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 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. ### OAuth finished in the browser but the account is still missing Try reconnecting LinkedIn and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot LinkedIn integration? Yes. ClawLink is the fastest way to connect Grok Bot to LinkedIn: link your LinkedIn account once in the browser and Grok Bot can call the LinkedIn API through 10 ready-made tools — no custom code or token handling. ### How do I connect LinkedIn to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect linkedin` to authorize LinkedIn. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect LinkedIn to Grok Bot? About two minutes. Sign in, click Connect next to LinkedIn in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring LinkedIn up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want LinkedIn working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Stack Exchange](https://claw-link.dev/grokbot/stack-exchange) — Search and browse questions, answers, and developer knowledge - [Zernio](https://claw-link.dev/grokbot/zernio) — Schedule social posts and pull analytics across platforms - [Grok Bot YouTube integration](https://claw-link.dev/grokbot/youtube) — Upload videos and manage channels