LinkedIn: Draft, schedule & publish posts in-workspace
LoginSign Up
See All Examples
For
FounderMarketingContent
Topics
Personal brandContent publishing
Used with
Marketing initiative tracker with Slack weekly rollups
LinkedIn

Draft, schedule & publish LinkedIn posts in-workspace

Author posts where the rest of your work lives, attach an image, and publish to your LinkedIn profile in one click — without bouncing into LinkedIn’s native composer or tracking drafts in a separate doc.

The composer in LinkedIn is fine. The problem is everything around it — drafts in Notes, references in Docs, the half-finished post you swore you’d publish three weeks ago. This brings the drafting and the publishing into the same workspace.

Drafts where the rest of the work happens

Most LinkedIn posting for founders looks the same: an idea while walking, a draft in Notes, a half-finished thought that gets back-burnered. The drafts pile up; very few of them make it to the actual composer. When they do, the context — the metric that prompted it, the screenshot you meant to attach, the link to the launch — is somewhere else.

This example moves the drafting surface into your workspace. Posts are first-class entities. You can list your drafts, attach an image to each, and publish to your LinkedIn profile when you’re ready. The same workspace holds the metrics, the deals, the dashboards — so the post and the thing it’s about live next to each other.

Posts and images as workspace entities

The LinkedIn Posts page lists every post you’ve drafted or published from this workspace. Each row links into a per-post editor for content, attachments, and publish status. Images attach to posts; the workspace stores them and forwards to LinkedIn at publish time. Once published, the post URN is captured so you can delete or reference the post later.

Draft, attach, publish in three steps

  1. Open the LinkedIn Post Editor. Compose the post body. Keep notes, links, and screenshots in the same workspace if you want to reference them while writing.
  2. Attach an image if you want one. The workspace stores the image as a post-image entity and forwards it to LinkedIn at publish time. One image per post.
  3. Publish to your profile. The post goes out as the authenticated user (your personal profile). The returned post URN gets saved against the post entity so you can find or delete it later.

Listing, image attachment, profile target

  • Show-all toggle — the LinkedIn Posts listing defaults to showing only the requesting user’s posts. Toggle “show all” on a shared workspace to see what teammates have authored from the same workspace.
  • Image attachment — one image per post, optional. Add it on the post-editor row.
  • Profile target — posts publish to your personal LinkedIn profile, as the authenticated user.
  • Replace a published post — delete and re-create. The workspace keeps the post URN so deletion is one click from the post row.

The drafting and the publishing happen on the same page. The pile of half-finished Notes drafts goes away.

From Notes pile to first-class posts

Two pages and a couple of entities — that’s all this workspace is. What makes it useful as an example is treating posts as first-class data: a row per post, an attached image per post, publish state captured alongside so deletion is one click later. The spec is what you change when the show-all default should flip for your team, when the post editor needs extra fields, or when a draft-review step belongs in the flow. The workspace re-renders; no code path to keep up with.

Try it in your Workspace