Approve it here, it posts there
The gap between a finished post and a published one is small, and it is where most content dies. You write it, you mean to post it, the week happens.
Connecting LinkedIn closes that gap. A post you approve goes out now, or at a time you pick, without another app and without copying anything into a box.
Connecting it
- 1In Inklined, open Settings and connect LinkedIn. You are sent to LinkedIn to approve it and handed back.
- 2The permission Inklined asks for lets it post as you, plus your name and profile photo so the preview looks right. It cannot read your feed, your messages or your connections.
- 3The connection belongs to you rather than to your organisation. Where more than one person shares an account, each publishes through their own connection and a post goes out as whoever wrote it.
What Inklined takes
- →Posts, published immediately or scheduled.
- →Scheduling is handled by Inklined rather than by LinkedIn, so a scheduled post goes out within five minutes of its slot.
- →Images and document posts, where the post carries them.
- →Only LinkedIn posts. An article is long-form and belongs on your blog, so Inklined will not push one here.
What happens to it
The first thing that happens to a transcript is that the names come out of it. People become role descriptors, so a participant is stored as “Host [GTM Consultant]” rather than by name. Companies become sector descriptors, so a client called Acme Corp is stored as “a B2B SaaS startup”. Email addresses, phone numbers, office addresses and profile links are removed. This runs once, on the way in, before anything else touches the text.
What is left is split into passages and indexed, so that when Inklined asks you something tomorrow it can show you the 40 seconds of the call the question came from rather than asserting that you said it.
Then a second rule applies, and it is the one that matters most if your calls are client work. Only speech attributed to you can become something you publish. On a typical consulting corpus most of the words belong to the other person, and offering those back to you as “something you said” is how somebody ends up publishing a client’s thinking under their own name. Anything that still names an organisation after all that asks you to confirm before it will draft from it.
One limitation worth stating rather than hiding: a client name that opens a sentence is not always caught, because “Sona ran this play” is shaped exactly like “Pricing pages need an owner”. The title check is the reliable one, and the confirmation step exists because no automatic check is enough on its own.
More on this: how Inklined works.
When it does not work
A connection that authenticates and then returns nothing looks exactly like a healthy one, which is why LinkedIn going quiet is hard to diagnose from the outside.
- Publishing stops working after a couple of months
- LinkedIn access expires on a fixed schedule and cannot be renewed silently. The connection is marked as needing attention, with the reason, and reconnecting takes one click. Nothing queued is lost.
- A scheduled post has not gone out yet
- The scheduler runs every five minutes, so a post can sit a few minutes past its slot. Longer than that and the connection is usually the cause rather than the schedule.
- The post went out under the wrong name
- The connection is per person, and a post publishes through the connection of whoever wrote it. On a shared account, check which person the draft is attributed to.
Questions
Sync runs every 4 hours. Setup steps checked against the product on 24 September 2026. Using something else? See what Inklined connects to.
The calls are already happening.
Start with the strategy session. No card needed for that part.