> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connie.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish as a LinkedIn company Page

> Publish text and images from an explicitly selected managed company Page through AI or a Workflow.

When enabled in your workspace, **Write LinkedIn Post** (`write-linkedin-post`) can publish personally or as a company Page you administer. Company publishing works in AI Chat, authorized MCP apps including ChatGPT, Workflow Actions and Workflow Agents.

Choose the connected LinkedIn account with **List accounts**, then use **List LinkedIn Managed Pages** in AI Chat or MCP to select the exact Page. Copy its complete binding:

```json theme={null}
{
  "senderUrl": "acc_your_connected_account",
  "company": {
    "accountId": "acc_your_connected_account",
    "id": "123456",
    "name": "Your company"
  },
  "content": "Your exact approved post"
}
```

Use the returned values; the example identifiers are placeholders. A public company profile does not prove that the account administers the Page. Connie checks current account access, working LinkedIn Classic access and provider-confirmed Page administration before publishing. An ambiguous account or Page requires selection. A missing, renamed, inaccessible or revoked Page causes a refusal; Connie does not switch to a personal post.

Leave `company` absent to keep personal publishing. An empty object, blank string or `null` is an invalid company selection. Existing personal Workflow configurations continue to publish personally.

To publish at a later time instead, personally or as a Page, see [Schedule LinkedIn posts](https://docs.connie.ai/tools/linkedin-scheduled-posts.md).

The post supports text up to 3,000 characters and up to five images, with 50 MB combined. Existing `imageUrl` accepts one URL or an ordered array. This company option adds no other media types. Reshares, quoted posts and explicit visibility/commenting controls remain separate AI-only actions.

### Approvals and retries

In AI Chat, approve the exact connected account, company Page, post text and images in the shared publication card. Cancelling or pressing Escape publishes nothing. MCP apps use their authenticated invocation and account selection. Workflow Actions and Agents keep their existing execution and approval controls. Configured Connie credits and account publishing limits still apply.

Keep the same invocation key when recovering a result. If publication is uncertain, check the selected Page on LinkedIn before deciding what to do. Never automatically republish. A recovered terminal receipt does not publish again or incur another tool charge.

### Saved Workflows

Select the existing **Write LinkedIn Post** Action or enable it for your Workflow Agent. Save the returned company binding in **Company Page**, or map the account and binding from variables. You can map the whole object (`{{input.company}}`) or its `accountId`, `id` and `name` values. The connected account must match `company.accountId`. The step author must retain account access; a manual run also checks the person starting it.

Page administration is rechecked when the Workflow runs. Managed-Page discovery and company invitation/balance tools remain AI-only; Workflow publishing reuses authorization internally. Company publishing is unavailable in Records Action columns and programs.

Successful output includes `postingIdentity.type`, `postingIdentity.id`, `postingIdentity.name`, `postingIdentity.url`, `accountId` and the existing `postUrl`. `senderId` and `senderUrl` continue to identify the individual account authorizing the publication. Existing content, image and character-count outputs retain their meanings. Downstream steps can use `{{Publish.postingIdentity.name}}` and `{{Publish.postUrl}}` when the publishing step is named Publish.

For an uncertain company publication, `success` is false, `status` is `uncertain`, `retryable` is false and `postingIdentity` is null; `requestedPostingIdentity` identifies the requested Page. This is not confirmation that a post appeared or that LinkedIn used the requested identity.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.