Guide
LinkedIn AI Agent: Publishing From Chat
LinkedIn is a narrower integration than most people expect, and knowing the boundary up front saves an afternoon. Here is exactly what an agent can do with a connected LinkedIn account.
Start with the boundary
LinkedIn gives third-party applications a deliberately small surface. You can publish on behalf of the account that authorized you. You cannot read the feed, you cannot read or send messages, and you cannot browse other people's activity. That is a platform decision, it applies to every legitimate tool equally, and no amount of configuration changes it.
So the honest description of a LinkedIn AI agent is: a publishing endpoint attached to something that can write. Which, if publishing consistently is the thing you struggle with, is genuinely the useful half.
Connect it in three steps
- Open openclawlaunch.com/integrations while signed in.
- Find LinkedIn and click Connect, then approve the account you want to publish as.
- Ask the agent to draft something and post it.
What the agent actually runs
A correct LinkedIn post is two calls, not one:
# 1. who am I posting as? returns the author URN
composio execute LINKEDIN_GET_MY_INFO '{}'
# 2. publish, passing that URN as author
composio execute LINKEDIN_CREATE_LINKED_IN_POST '{"author":"urn:li:person:XXXX","commentary":"What I learned running an agent for six months."}'LINKEDIN_GET_MY_INFO— identity lookup; supplies theauthorURNLINKEDIN_CREATE_LINKED_IN_POST— publish; needsauthorandcommentary, with optional visibility settings
If you see an author-related error, this two-step is the thing that was skipped. It is the single most common LinkedIn setup failure.
Draft in chat, publish deliberately
A recommendation, offered as opinion rather than instruction: keep a human approval step between the draft and the post. LinkedIn is a professional identity, published posts are visible to people whose opinion of you matters, and an agent with a standing instruction to publish is one badly-worded generation away from an awkward morning. Ask it to draft, read the draft, then say post.
Where automation genuinely earns its place is the boring part: turning something you already wrote elsewhere — a changelog entry, a set of notes, a document — into a post shaped for the platform, at a time you would otherwise have forgotten.
Things worth asking for
- “Turn these release notes into a LinkedIn post. Show me the draft first.”
- “Rewrite that with a stronger first line — the first two lines are all anyone sees.”
- “Post the version we agreed on.”
- “Draft three angles on this topic and let me pick one.”
Limits and revoking access
100 executed actions a day on free trial and Lite, 1,000 on Pro — well beyond any sensible posting cadence. LinkedIn applies its own rate limits on top, which matters far less for publishing than it would for reading. Disconnect from the integrations page at any time, or revoke from LinkedIn's own permitted-services settings.
Frequently asked questions
Can the agent read my LinkedIn feed or DMs?
No, and this is a LinkedIn decision rather than ours. LinkedIn's API is deliberately narrow for third-party apps: publishing on your own behalf is supported, general feed reading and messaging are not. Anyone promising you a LinkedIn agent that scrolls your feed is either scraping — against LinkedIn's terms, and a good way to lose the account — or overselling.
The post failed with an author error. What is missing?
LINKEDIN_CREATE_LINKED_IN_POST requires an author value — a LinkedIn URN identifying who is posting — alongside the commentary text. It is not optional and it is not your public profile URL. The agent gets it by calling LINKEDIN_GET_MY_INFO first, which is why a well-formed run is always two calls rather than one.
Will an agent-written post get me reach?
Not by itself, and it is worth being honest about that. LinkedIn rewards posts that hold attention and start conversations; generic AI-written copy is recognisable and performs accordingly. The genuinely useful pattern is the agent as a drafting and scheduling hand — you supply the substance and the specifics, it handles the writing mechanics and the publishing.
Can it post to a company page?
The author URN is what determines where a post lands, and posting as an organization requires the connected account to hold the appropriate admin rights on that page. If the permission is not there, the call fails at LinkedIn rather than in the agent.