Can ChatGPT Post on LinkedIn? What Works and What Does Not
ChatGPT on its own cannot touch LinkedIn. It has no LinkedIn account, no permission from you, and no way to reach LinkedIn’s servers. What it can do is talk to a connector — a small service you add to ChatGPT that holds your LinkedIn permission and does the posting for it. That is the whole trick, and it comes with real conditions worth knowing before you spend an evening on it.
So can ChatGPT post to LinkedIn or not?
It can, once you add a connector built on LinkedIn’s official posting permission. Without one, asking ChatGPT to “post this to LinkedIn” gets you the text back in the chat window and nothing more.
The connector standard is MCP (Model Context Protocol — an open way for AI assistants to talk to outside tools). Kalovio is an MCP server for LinkedIn: you connect your own LinkedIn account to it once, then ChatGPT can ask it to publish, schedule, or draft posts. Kalovio holds the LinkedIn permission; ChatGPT never sees your LinkedIn login or token.
Here are the conditions, stated plainly, because most pages skip them.
| Requirement | Detail |
|---|---|
| Plan | Developer Mode is on paid plans — Plus, Pro, Team, Enterprise, Edu. Not the free tier. |
| Device | Web only. Developer Mode connectors are not available in the mobile apps. |
| Setup | Settings, Connectors, Developer Mode, then Plugins, plus, New Plugin. Auth set to OAuth. |
| Per chat | The connector is off by default in each new conversation. You switch it on from the tools menu. |
| Codex | Does not carry over. Codex is a separate app with its own connections. |
What does not work, and why
Three things surprise people. None of them are bugs in the connector; they are how ChatGPT itself is built.
1. You cannot attach an image in chat and have it reach the connector
This is the big one. You can drop a photo into a ChatGPT conversation, ChatGPT can look at it and describe it — but it cannot hand that file to a connector. Tool calls carry plain text arguments (JSON — a simple structured text format), and MCP defines image content for tool results, not for tool inputs. So there is no channel for the file to travel down.
Claude has the same gap. This is not a ChatGPT-only problem.
The fix is a separate upload step. Ask for your upload link, open it in a browser tab, drop the images in, and they land in your image library with short IDs. Then tell ChatGPT which ones to use:
- “Give me my Kalovio upload link.”
- Open the link, drag in one or more images or a PDF.
- “Publish my post with these images: img_a, img_b.”
It is one extra step and it works the same way in every AI app, which is why it stays the default path.
2. The connector is off in every new chat
A Developer Mode connector is not automatically active. Start a fresh conversation and it sits dormant until you enable it from the tools menu in that conversation. Forget this, and ChatGPT will confidently tell you it has no way to post to LinkedIn — which is true at that moment, and misleading about your setup.
If posting worked yesterday and does not today, check this first. It is the single most common cause.
3. Connecting in ChatGPT does not connect Codex
ChatGPT and Codex are separate applications. Adding a connector in ChatGPT on the web does nothing for Codex, and signing in once does not cover both. Each app connects and authorises on its own. Kalovio is not promoted for Codex for this reason.
Why asking ChatGPT “are you connected?” is unreliable
It feels like the obvious test. It is close to useless.
ChatGPT does not have a clean, honest view of its own tool list to describe back to you. Ask “are you connected to LinkedIn?” and you are asking it to introspect and narrate — two things language models do badly. It will often say no when the connector is live, or say yes when the connector is switched off in that chat. Both answers are guesses dressed as facts.
The reliable test is a real request. Do not ask about the connection. Ask for an action and watch what happens: “Use Kalovio to check my LinkedIn account status.” If the connector is live, you will see a tool call run and get a real answer about your account. If it is off, you get an apology and no tool call. The tool call either happens or it does not, and that is a fact rather than an opinion.
A second good probe is “Ask Kalovio to list my drafts.” Same logic: it forces the connector to be used rather than described.
What actually works once you are connected
With the connector on, you write in plain language and confirm what you see. The everyday flow:
- Publish now. “Write a post about what I learned shipping this week and publish it.” You get a preview back, you say yes, it goes out.
- Schedule. “Schedule that for Tuesday at 9am.”
- A weekly queue. Set your posting times once, then drop posts into the next free slot instead of picking a date each time.
- Drafts. Create, list, edit and delete drafts without leaving the chat.
- Images and carousels. One image, a swipeable set of two to nine, or a PDF document carousel — all from files you uploaded via the link.
- A voice profile. Save how you write once so posts stop sounding like a press release.
- Link-click tracking. Links can go out as short kalovio.com/r/ links so you can see clicks.
Posts cap at 3000 characters, which is LinkedIn’s own limit. A caption is optional when there is an image or PDF attached, so an image-only post is fine.
One caveat on the last two formats. Multi-image carousels and PDF document posts go through LinkedIn’s newer versioned interface, which may not be switched on for every self-serve app. If yours is not, you get a clear message rather than a silent failure, and text and single-image posts still work on the older, well-established path.
The confirm step is not optional, by design
Publishing, scheduling, queueing and deleting are all two-step. The first call returns a preview plus a signed token (a tamper-proof stamp) covering the exact text, image, timing and mentions. Nothing reaches LinkedIn until a second call confirms with a matching token. That is what stops a stray instruction inside some web page you pasted from quietly publishing on your behalf.
What no connector can do on LinkedIn
These limits come from LinkedIn, not from ChatGPT or the tool:
- It cannot read posts it did not create. The permission for that,
r_member_social, is closed to self-serve apps. - Access expires around 60 days. Self-serve apps get no refresh token, so you reconnect periodically.
- No real engagement analytics. Impressions and follower stats need LinkedIn’s partner-gated Community Management API. Link-click tracking is not the same thing.
- No DMs, no connection requests, no lead scraping. Not supported, not planned.
- Tagging a company page needs that page’s numeric ID; LinkedIn offers self-serve apps no lookup by name.
On the rules. LinkedIn’s API Terms of Use, section 3.1(26), restricts using the APIs “to automate posting on the LinkedIn Services”, with no written exception for member-approved posting. Anyone promising “zero risk” is overselling. The defensible position is narrower: the permission is open and self-serve, you grant it yourself through LinkedIn’s own consent screen, you approve the exact wording of every post, nothing is scraped, and you can revoke access from your LinkedIn settings at any time.
Short version
ChatGPT can post to LinkedIn through a connector, on a paid plan, on the web, with the connector switched on in that conversation, and with images uploaded through a link rather than dropped in the chat. Everything else — writing, scheduling, queueing, drafting — behaves the way you would hope. If you are on the free plan or on mobile, Claude’s custom connector is the easier route, and it works on Claude’s free plan.
Questions people ask
Can ChatGPT post to LinkedIn without a connector?
No. ChatGPT has no built-in LinkedIn integration. Without a connector it can write the post text for you, but it cannot publish it. You need an MCP connector such as Kalovio that holds your LinkedIn permission.
Do I need ChatGPT Plus to post on LinkedIn?
You need a paid plan of some kind. Developer Mode, which is where custom connectors are added, is available on Plus, Pro, Team, Enterprise and Edu — not on the free tier. It is also web only, so the mobile apps will not work.
Why does ChatGPT say it cannot post to LinkedIn when I already added the connector?
Almost always because the connector is switched off in that conversation. Developer Mode connectors start off in every new chat, and you enable them from the tools menu. Turn it on, then ask for an action rather than asking whether it is connected.
Can I attach an image in ChatGPT and have it posted to LinkedIn?
No. ChatGPT cannot pass a chat attachment to a connector, and neither can Claude. Ask for your Kalovio upload link, drop the images or PDF there, then tell ChatGPT which image IDs to use in the post.
Does my ChatGPT connector also work in Codex?
No. ChatGPT and Codex are separate apps and connect independently. Adding and signing into a connector in ChatGPT on the web has no effect in Codex.
Is it better to use Claude or ChatGPT for LinkedIn posting?
Claude is simpler to set up: a custom connector works on the free plan, with no Developer Mode step and no per-chat toggle. ChatGPT works well too, but needs a paid plan, the web app, and the connector enabled in each conversation.
Sources
Try Kalovio free
Run your LinkedIn from a chat with Claude or ChatGPT. Add this as a custom connector — free while in beta, and you approve every post before it goes live.
https://kalovio.com/mcpHow to connect