How to connect LinkedIn to OpenClaw

The ClawHub skill teaches OpenClaw about LinkedIn, but the calls run through the ClawLink plugin and your connected account. Make sure LinkedIn 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.

Reconnect LinkedIn from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

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.

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.

LinkedIn separates permissions by what you are posting as, so the first question is whether the failing call is a member post or an organization one. A member post needs the member posting permission on the grant; an organization post needs the organization posting permission and an admin role for the connected account on that specific page. A partial approval on the consent screen is the other common cause — LinkedIn lists what it is granting, and a connection that was approved without the write permission will read fine and fail on every publish. Reconnect from the dashboard and accept the full set. If personal posts succeed and only the company page fails, stop looking at the connection and check your role on the page in LinkedIn itself.

Ask the agent to diagnose it:

Call linkedin_get_my_info and tell me exactly which LinkedIn account is connected. Then try a draft member post and tell me whether it succeeds, but do not publish anything without asking me first.

LinkedIn grants are time-limited and are also invalidated when you change your password or revoke third-party access, so a connection that worked last month and fails today has usually simply expired rather than broken. Reconnecting from the ClawLink dashboard reissues it. Before assuming that, check that the failure is on every call rather than one: if reads still work and only publishing fails, the grant is alive and you are looking at a permissions problem instead.

Say which one in the prompt, because the default is you. The tools take the author explicitly, so an instruction that just says "post this on LinkedIn" resolves to a member post under your own name. Naming the company page in the request, and confirming the agent read your admin role back before it published, is the reliable way to control it. This is worth checking on the first post rather than the fifth, since a member post cannot be converted to an organization post after the fact — it has to be deleted and republished.

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.

Yes. ClawLink is the fastest way to connect OpenClaw to LinkedIn: link your LinkedIn account once in the browser and OpenClaw can call the LinkedIn API through 10 ready-made tools — no custom code or token handling.

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink LinkedIn skill from ClawHub, then you click Connect in the dashboard to authorize LinkedIn. OpenClaw calls the tools from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to LinkedIn in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app 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 LinkedIn working from chat.

No. That requirement belongs to the do-it-yourself route, where you register an app, request the products that grant posting permissions, and wait to be approved before you can post anything at all. ClawLink's connection runs through an already-approved app, so the only screen you see is LinkedIn's consent screen listing what is being granted. You keep your own account's reach: the agent can do what you can do, and LinkedIn's own rules about what an account may post still apply on every call.

Posting as yourself and posting as an organization are different permissions on LinkedIn, and the second one also depends on your role. Member posts go out under your own name. To publish on a company page, the connected account must hold an admin role on that page, and the connection must carry the organization posting permission — if either is missing the call fails even though personal posts work fine. The quickest way to tell them apart is to have the agent post to your profile first; if that succeeds and the page post does not, the problem is the page role or the organization permission, not the connection.

The connection uses LinkedIn's OAuth flow against LinkedIn's official API, so you approve a named set of permissions on LinkedIn's own screen, no password is ever entered anywhere but LinkedIn, and you can revoke access from the ClawLink dashboard at any time. That is a meaningfully different risk profile from the browser-automation approach many guides recommend, which drives a logged-in session, is against LinkedIn's terms, and can get an account restricted. The judgement call left to you is publishing: posts and comments are public and immediate, so ask the agent to draft and wait for approval rather than letting it post directly.

No. LinkedIn's API is deliberately narrow, and this toolset reflects that: it can publish posts, share an article or URL, comment on a post, read your own profile information, and work with images for post media. There is no feed reading, no messaging, no connection management, and no profile scraping of other people. If a guide promises an agent that browses LinkedIn and messages prospects, it is describing browser automation rather than the API, with the account risk that carries.

The ClawHub skill teaches OpenClaw about LinkedIn, but the calls run through the ClawLink plugin and your connected account. Make sure LinkedIn 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.