LinkedIn integration: company pages and personal profiles
Two LinkedIn integrations, one for company pages and one for personal profiles. Which to pick, what does not come across, and the consent conversation before you connect a colleague.
LinkedIn is two integrations, not one, because LinkedIn treats a company page and a person's profile as different things.
LinkedIn company watches a company page and imports its posts.
LinkedIn user watches one person's profile and imports what they post.
Everything after that choice behaves the same. Pick the type that matches your source. To get a company page and its CEO into one feed, create both, pointing at the same mix.
Which one you need
You want | Integration | Source URL |
|---|---|---|
What corporate communications publishes | LinkedIn company |
|
A leader's own posts | LinkedIn user | The profile URL as the browser shows it |
Both, in one feed | Both, same mix | Two integrations |
A hashtag, a group, or a search | Not supported | Use a different source type |
Open the page on LinkedIn and copy the address bar. A post URL, a search result or a feed URL will be rejected.
Talk to the person before you connect their profile
A company page is a corporate channel. A personal profile is not, even when the person is your CEO.
People post about work, and they also post about a conference they enjoyed, a colleague's promotion, a job change, an opinion on their industry. Connecting the profile means all of that can land in an internal feed, in front of everyone, without them choosing it each time.
So: ask first, and agree what happens.
Get their explicit agreement. Not a mention in a meeting. An actual yes to the sentence "your LinkedIn posts will appear in the employee app".
Leave auto-publish off, at least at the start. An editor sees each post before the company does. Most organisations keep it that way permanently for personal profiles.
Agree how it ends. Someone should be able to say "take this out of the app" and have it happen the same day.
Check whether it needs consultation. In a co-determined workplace, feeding a named individual's content into an employee app can be a topic for the works council. See Works council.
This is the part customers most often skip and most often regret.
What comes across, and what does not
The integration imports posts: the text, and the image that goes with them.
It does not import:
Documents and carousel PDFs
Polls
Comments and reactions from LinkedIn
That matters more on LinkedIn than on other networks, because documents and polls are exactly what corporate pages post. A post that is mostly a carousel arrives as a card with a line of text and nothing to look at.
Two ways to deal with it:
Leave auto-publish off on high-volume pages, so an editor catches the empty ones.
Post the substance twice. Where a carousel matters internally, an editor rebuilds it as a long post or an image card in tchop, and lets the automated card link out.
When people change jobs
A connected personal profile keeps posting after that person leaves your organisation. The integration has no idea anything changed, and their posts about their new employer arrive in your employee app.
Nobody notices this on day one. It shows up weeks later, usually to an audience.
Add it to the offboarding checklist: review LinkedIn user integrations when someone moves on. It takes one look at the integrations list, which shows the source URL and who created each connection.
Common errors
Error right after setup. Check the URL form. Company pages need /company/. A profile URL copied from a search result often carries tracking parameters that break it.
A company page works, a person's profile does not. They are separate integration types. A profile URL in a LinkedIn company integration is rejected by design.
Posts arrive as bare text with no picture. Either the post carried no image, or it was a document or carousel post, which do not come across.
Some posts are missing entirely. Member-only and restricted posts cannot be imported. Only what a public visitor sees is available.
Error on a profile after a rebrand or a name change. LinkedIn URLs can change with them. Paste the current URL from the address bar.
Nothing arrives, status Active. Check the source's own posting history before looking for a fault. Many company pages post less often than people assume.
Questions from internal comms teams
Do we need a LinkedIn admin or an API key? No. The integration reads public posts. There is no login on your side.
Can we connect ten employees as brand ambassadors? Ten profiles means ten integrations, and ten consent conversations. Doable, and worth thinking through before you promise it.
Can we import LinkedIn newsletters or articles? Not as their own source type. Posts are what comes across.
Can two profiles feed the same mix? Yes. Any number of integrations can point at one mix. The same source twice in the same mix is rejected.
How fast do posts appear? Within about half an hour, the same interval as every source type.
What happens to cards if we delete the integration? They stay in the mix. Removing the connection stops the sync, it does not clean up history.
Decide these two things first
Decide company page or personal profile. If it is a profile, have the conversation first. Then keep auto-publish off until you have watched a week of posts arrive.
The shared settings behave the same as everywhere else. How integrations work covers mix, name, backfill and auto-publish in one place.



