# LinkedIn — Create post

Automatically create post on linkedin.com. Publish a text post to your LinkedIn feed now, or schedule it for a later date and time. Without scheduleDate/scheduleTime it creates a real, public post under your account immediately — not a draft or preview — and returns the post's link. With scheduleDate (M/D/YYYY) and scheduleTime (a quarter-hour such as "9:45 AM") it queues the post in LinkedIn's Scheduled posts instead and returns when it will publish; an identical post already queued is reported, not duplicated. Plain text with optional @mentions and a single image (images cannot be scheduled); polls and articles need a different flow. dry_run stops before the final Post/Schedule click. Requires being logged into LinkedIn. To list or cancel scheduled posts, use get_scheduled_posts / remove_scheduled_post.

- Site: linkedin.com
- Address: `reduck/linkedin.com/create_post`
- Updated: 2026-10-22 (v56)
- Author: Reduck AI (reduck)

## Run it

Ask an AI agent connected to Reduck over MCP (`https://mcp.reduck.ai/mcp`) to run `reduck/linkedin.com/create_post`, or run it from a terminal:

```bash
npx @reduck-ai/cli@latest run --script reduck/linkedin.com/create_post
```

## Input

- `text` (string, required): The post body. Plain text; newlines preserved. Any bare URL in the text auto-unfurls into LinkedIn's own link-preview card. Posted publicly ("Anyone") under the logged-in member. Confirm the exact text with the user before running this -- it creates a real, public, immediate post under their account.
- `dry_run` (boolean, optional): When true, everything runs -- the composer opens, the body is typed, mentions are resolved and any image is attached and confirmed -- and then the run stops before clicking Post. Nothing is published: posted comes back false, url and shareUrn null, and dry_run true. Use it to verify text, mentions and an image are accepted without creating a real public post.
- `mentions` (array, optional): Person or organization names to @mention, appended in order at the end of text (each as ' @Name'). Confirm each name with the user before running. If a name is ambiguous (multiple people share it exactly), the run throws listing candidates by headline -- re-run with the name plus enough of their headline/company/org for LinkedIn's own typeahead to narrow to exactly one match.
- `attachment` (string, optional): A single image to attach, bound through the platform's own file channel and handed to the media editor's own file input. Preferred over imageBase64: it carries the bytes outside the argument payload, so there is no payload ceiling. Pass this or imageBase64, not both. Cannot be combined with scheduleDate/scheduleTime, for the same reason imageBase64 cannot.
- `imageBase64` (string, optional): A single image to attach, base64-encoded (no data: prefix). Optional; prefer the `attachment` input, which has no payload ceiling. Cannot be combined with scheduleDate/scheduleTime -- LinkedIn's Schedule modal wipes the composer, which would discard the staged image. Multi-image carousels are not yet supported by this script.
- `scheduleDate` (string, optional): Schedule the post instead of publishing immediately: the date to publish, as M/D/YYYY (e.g. "8/14/2026"). Must be a future date, and requires scheduleTime.
- `scheduleTime` (string, optional): Time of day to publish when scheduling, as one of LinkedIn's own quarter-hour options (e.g. "9:15 AM"). Requires scheduleDate.
- `imageFilename` (string, optional): Filename for the imageBase64 attachment, e.g. chart.png. Required when imageBase64 is set. Not used by the `attachment` input, which carries its own name.
- `imageMimeType` (string, optional): MIME type of the imageBase64 attachment; inferred from imageFilename when omitted. Not used by the `attachment` input.

## Output

- `url` (string | null, required): Post permalink (resolves to the post); feed it to delete_post or get_post. Null when scheduled (no permalink exists until the post actually goes live), and null on a dry run, where nothing was published.
- `posted` (boolean, required): True once this run's write immediately published a new post. False when scheduled (see `scheduled`), or when an identical post/schedule already existed and nothing new was created (see already_present / alreadyScheduled). Always false on a dry run.
- `shareUrn` (string | null, required): The post's share urn, e.g. urn:li:share:7475847938603192320. On an already_present hit this is the existing post's activity urn instead. Null when scheduled, and null on a dry run.
- `scheduled` (boolean, required): True if this run scheduled a post (new or already-existing) instead of publishing immediately.
- `account_used` (object, required): The real account the post was published/scheduled under, echoed from the session/UI.
- `scheduledFor` (string | null, required): When scheduled is true, the scheduled-posts panel's own confirmation string, e.g. "Preview of the scheduled post that will be published on Mon August 17, 2026 at 1:00 PM, click to see detail view". Null otherwise.
- `already_present` (boolean, required): True if an immediate post with this exact text was already found on the account's own activity before attempting to publish -- the run stopped there instead of creating a duplicate; url/shareUrn point at that pre-existing post. Never true on a scheduling run (see alreadyScheduled for that case).
- `alreadyScheduled` (boolean, required): True if a scheduled post with this exact text already existed in the account's Scheduled posts queue before this run -- nothing new was scheduled; scheduledFor describes the existing entry. Only meaningful when scheduleDate/scheduleTime were passed.
- `verified_on_page` (boolean, required): True if the script independently reloaded and confirmed the write: for an immediate post, the permalink actually renders the text; for a scheduled post, the Scheduled posts management panel actually lists an entry matching this body; for an already_present/alreadyScheduled hit, this is always true (the existing entry was what was matched). Always false on a dry run, where nothing was published to re-read.
- `dry_run` (boolean, optional): True when this run stopped before clicking Post and published nothing. The body was still typed, the mentions still resolved and any image still attached and confirmed — only the publish was skipped.
- `mediaAttached` (boolean | null, optional): True when an image was provided (via the `attachment` input or imageBase64) and confirmed staged -- a remove-media control appeared -- before publishing. Null when no image was requested. Meaningful on a dry run too: it reports whether the image really staged, which is the half of this script most likely to break.

## FAQ

### What does "LinkedIn — Create post" do?

Publish a text post to your LinkedIn feed now, or schedule it for a later date and time. Without scheduleDate/scheduleTime it creates a real, public post under your account immediately — not a draft or preview — and returns the post's link. With scheduleDate (M/D/YYYY) and scheduleTime (a quarter-hour such as "9:45 AM") it queues the post in LinkedIn's Scheduled posts instead and returns when it will publish; an identical post already queued is reported, not duplicated. Plain text with optional @mentions and a single image (images cannot be scheduled); polls and articles need a different flow. dry_run stops before the final Post/Schedule click. Requires being logged into LinkedIn. To list or cancel scheduled posts, use get_scheduled_posts / remove_scheduled_post.

### How do I automatically create post on linkedin.com?

Ask an AI agent connected to Reduck to run reduck/linkedin.com/create_post, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/linkedin.com/create_post

### Is there a linkedin.com API to create post?

You do not need one. "LinkedIn — Create post" drives the real linkedin.com pages in a browser, so it works whether or not linkedin.com offers an API for this.

### What information do I need to provide?

Required: text. Optional: dry_run, mentions, attachment, imageBase64, scheduleDate, scheduleTime, imageFilename, imageMimeType.

### What does it return?

It returns url, posted, dry_run, shareUrn, scheduled, account_used, scheduledFor, mediaAttached, already_present, alreadyScheduled, verified_on_page.

### Do I need to be logged in to linkedin.com?

Yes. It acts as you on linkedin.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the linkedin.com cookies saved by the Reduck extension.

### Does it change anything on linkedin.com, or only read data?

It makes changes on linkedin.com, like sending, posting, booking or buying something.

### How do I run it?

Ask an AI agent connected to Reduck to run reduck/linkedin.com/create_post, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/linkedin.com/create_post

### Who maintains it?

It is part of Reduck's official curated catalogue.

Source: https://reduck.ai/explore/scripts/reduck/linkedin.com/create_post