How to schedule LinkedIn posts

To schedule a LinkedIn profile post, open Start a post, write it, select the clock, choose a date and time, then Next → Schedule. LinkedIn lets you choose a time 10 minutes to 3 months ahead. You don't need a separate publishing tool for that.

A scheduling tool becomes useful when you want a shared queue, more than one network, or an AI agent preparing posts for your review. Building directly on the API is another option, but the documented Posts API publishes when called; your application has to keep the queue and make the call when the post is due.

LinkedIn's own help pages and API docs (version 202610), and Buffer's own help, were checked on October 26, 2026. This is a documentation check, not a live scheduling or posting test. The sources are linked beside the claims below.

Choose the route that fits

Schedule a post on your personal profile

These are LinkedIn's documented controls, not steps inside Flaghand:

1. From LinkedIn's home feed, select Start a post and compose your update.
2. Select the clock in the composer. On the mobile app, start from Post and use the clock there.
3. Choose the date and time, between 10 minutes and 3 months from now. You can enter a precise time; the menu's half-hour intervals aren't mandatory.
4. Select Next, review the post and its displayed time, then Schedule.
5. To find it again, reopen the composer and clock, then View all scheduled posts. Open an item to preview it. Its More menu offers Modify schedule and Edit post; the delete control removes it after confirmation.

LinkedIn converts the chosen time to UTC using your device's time zone. Check the device setting and the time shown above the draft, especially when travelling. Don't assume a teammate's local 9 am is your local 9 am.

What can and can't use the profile scheduler?

LinkedIn's current Schedule posts help describes scheduling feed posts and explicitly excludes events and jobs. It doesn't enumerate every supported attachment format, and it doesn't list polls or service posts in that exclusion. That omission is not a guarantee that every composer variant can be scheduled: check that the clock is available for the post you are making.

In particular, don't copy a Page-specific restriction into a profile guide, or use an API's supported-format list as proof that the same format works in LinkedIn's native clock. They are different publishing routes.

Schedule a post as a LinkedIn Page

For a Page, enter its super admin or content admin view, then Page posts → Start a post → clock. Choose the time, select Next, finish reviewing and select Schedule. LinkedIn's Page scheduling instructions also cover the mobile route through Dashboard → Page posts → Post.

The Page scheduling overview gives a different window: 1 hour to 3 months ahead. It also supports scheduling newsletter articles, but lists these as unsupported: events, multiple photos, reshares, polls, jobs and service posts. Administrators can edit, reschedule, publish immediately or delete queued posts, including posts scheduled by other administrators.

Those are the Page scheduler's restrictions, not a statement that LinkedIn's API cannot publish multiple photos or polls. It can, with the right permission and a tool that implements them.

Use a scheduling tool when the native queue isn't enough

A useful tool should make it clear which account will publish, what content it can actually send, when it will do so, and who has the authority to release it. A calendar entry or an AI-generated draft is not evidence that a post has been scheduled, much less published.

Two options illustrate different needs; this isn't an exhaustive ranking:

• Buffer, for profiles and Pages. Its LinkedIn guide documents scheduling to both, with text, links, images, videos, GIFs and PDF documents. It supports up to 20 images, or one video, GIF or PDF per post. PDF scheduling is web-only, not available in its mobile app; it explicitly doesn't create LinkedIn polls. Buffer is the relevant option here if you need company Page publishing. Its guide also explains reconnecting an expired or revoked connection. Check the required features in its current plan before choosing it.
• Flaghand, for an agent drafting and a person deciding. Its merged LinkedIn implementation supports personal profiles, not company Page publishing: text, 1 to 20 photos, one MP4, one PDF document, a link card or a poll. These are alternative content types, not a promise that they can be combined. Agents can draft, upload, check and request approval through its API or MCP; their tokens cannot approve, schedule or publish. Only the owner can approve the exact snapshot and proposed time with a passkey. LinkedIn post read-back is unavailable with its current permissions, so it reports the returned post link, not a verified match to the live post.

Flaghand sign-up is not open yet. It is an early-access option, not an account you can create by following this article today. Join the Flaghand waitlist. Its public drafts and media reference describes the implemented formats; the agent documentation explains the approval boundary. Account setup and the Flaghand-specific scheduling walkthrough are not part of this public guide while sign-up is closed.

Schedule through the LinkedIn API: your app owns the clock

Share on LinkedIn is the self-serve product that grants w_member_social. The member authorizes your app with OAuth; that permission lets it create posts as the authenticated personal profile. Posting as an organization is a different permission, w_organization_social, with a qualifying Page role.

Use the current Posts API, which replaces ugcPosts: POST /rest/posts, with Linkedin-Version: 202610 and X-Restli-Protocol-Version: 2.0.0. Its post schema accepts only lifecycleState: "PUBLISHED" on creation. It documents publishedAt as the time the content was published, not as a future scheduling instruction. There is no documented future-time scheduling parameter in that create contract. DRAFT appearing in a response-state list is not permission to create a delayed post.

For an API-based scheduler, keep the approved content and intended instant in your own system, then submit the publish request when due. Your system must handle authorization failures, media processing and uncertain outcomes; an unanswered request is not proof that nothing published. Don't blindly replay it. A successful create returns 201 and the post ID in x-restli-id. Save that result separately from your queue's intended time.

What a personal profile can post through it

That is LinkedIn's API surface, not a claim that every scheduling tool supports every row. In particular, a PDF document is not the API's advertising-only carousel format, and an article link card is not a native newsletter edition.

Write permission isn't read permission. Retrieving member posts needs r_member_social. LinkedIn's Community Management overview calls it a closed permission and says it isn't accepting access requests. An ordinary Share on LinkedIn app can't promise to read a published post back merely because it can create one. Reading the parent before a repost is also a separate permission problem. See the personal-profile API guide for comments, mentions and the other permission boundaries.

Before you leave a post in any queue

Check the author, the complete text, the media, the intended date and the time zone. If you move a post between tools, make sure the original queue won't publish it too. Keep the platform's accepted result distinct from a planned slot; when the tool can't verify the live post, inspect its link yourself rather than treating "scheduled" as "verified".

For a simple post, LinkedIn's own scheduler is the shortest route. Use a broader tool for a real workflow need, and build your own API queue only if you want to own its operational work. You can check the draft's feed appearance in the free LinkedIn post preview without a Flaghand account; it does not schedule or publish.