Claude and LinkedIn: Understand the Connection Before Posting

Claude can use a connected service to act on LinkedIn when that service exposes the relevant tools and has the required platform access. Claude's ability to call a tool and the service's permission to publish are separate parts of the workflow.

Choose the right connection instructions

Anthropic distinguishes remote connectors from locally configured servers. Its remote connector guide explains that remote connections originate from Anthropic's infrastructure. A server reachable only on your laptop or private network is therefore a different setup problem from a public remote service.

Use the instructions for your Claude client and the service you selected. Do not paste a desktop configuration file into an unrelated web settings screen. For FeedSquad-specific information, start with the Claude connection page.

Understand the two permissions

First, Claude needs permission to access the connected service. Separately, that service needs permission to act on the LinkedIn account. Signing in to one does not establish the other.

LinkedIn's Share on LinkedIn documentation identifies w_member_social as the permission for posting on behalf of an authenticated member. It is a scope, not a publishing endpoint. Organisation posting and other actions have their own requirements; do not assume member access proves they are available.

Token handling is the integration provider's responsibility to document. A brokered design can keep platform credentials out of model-visible results, but that does not make every action through the connection harmless or remove the need to control permissions.

Start with a draft-only request

A useful first instruction is:

Prepare a LinkedIn draft using these approved notes. Do not publish. Show the target account, final text, attached media and saved draft status.

Inspect the tool result. Tool names are service-specific: a name such as create_post does not universally mean “save draft,” and it should not be treated as proof of publication either.

Check a second surface, such as the service's calendar, for the saved item. Correct a fact and verify that the saved version changes too.

Make scheduling explicit

Once the draft is ready, state the date, timezone and destination. Review the exact artifact before authorising a public action. If the service supports approval separately from publishing, confirm what each state means.

For example, an approved item with no scheduled time might be ready for later use rather than about to publish. Ask the service to show the actual stored state instead of inferring it from “done.”

Diagnose a failed connection

Separate service authentication, LinkedIn account access, unsupported content and publishing failure. Reconnecting the service will not necessarily fix a missing LinkedIn permission. Rewriting the post will not fix a revoked account connection.

Record the operation, time, account and non-sensitive error details for support. Never include raw access tokens in a shared troubleshooting note. Use the scheduling acceptance test before relying on the connection for a launch.