Skip to content
OpenPostDocs
OpenPostDocs

Create and publish

Write, review, and publish destination-specific versions of a post.

Choose New post in the workspace where you want to publish. Select the connected accounts, then write the update you want to share. For example, you can start with one launch announcement and give its LinkedIn and X versions different openings. Each selected account gets its own destination version, called a variant.

Make each destination ready

Open each destination in the composer and adjust its text, format, media, and provider settings. Check the account, text, and file order in the preview. A file or format that works for one provider may not work for another. If the composer flags a limit or required field, fix that destination before publishing.

Save a draft or write a thread

If the post needs another pass, leave it as a draft. The composer saves draft changes while you work; wait for its saved indicator, then find the post under Publications → Drafts. For a thread, add segments in reading order, then preview the whole sequence for each destination.

Polls

Choose Add poll below the post text, then enter a question, answers and voting duration. Introductory post text is optional. The poll shows how many selected destinations can receive a native poll.

Under Poll versions, choose what each account receives:

  • Native poll uses the shared question and answers.
  • Custom poll lets a compatible account use different poll content.
  • Text version appends the question and numbered answers as ordinary text. Expand its preview or choose Customize post text to edit that account's version.
  • Post without poll keeps that account's post text and media without the poll.

You can also exclude an account from the post. OpenPost does not choose a fallback or remove accounts automatically. Fix native poll conflicts, such as media attachments or an answer exceeding an account's limit, before publishing. Drafts can save while choices are unfinished.

Each thread segment can have its own poll. Destinations that combine a thread into one post need text versions or explicit omissions. Older account-specific polls remain available in that account's settings.

Media

Upload files in the composer or choose an existing file from Media. If a video needs trimming or captions, prepare it in the Video Editor or Quick Cut, then attach the finished export. Check the media requirements shown for every selected account before you send.

Schedule and calendar

In the composer, choose Schedule, pick a date and time, and check the timezone shown in the dialog before saving. The post stays Scheduled until OpenPost queues it for delivery.

Open Publications → Calendar to check where the post landed. Use week view to inspect times or month view to see a wider plan. Open the post if you need to check its destinations or make a change.

Delivery states

The post and its destinations can show Scheduled, Queued, Publishing, Published, or Failed. After delivery starts, check the post in Publications instead of treating its calendar slot as proof it published. For partial delivery, retry only the failed destination as described above.

Change a schedule

Open a scheduled post to change its date or time. You can also drag a scheduled item to another future slot in Calendar; the drop saves the new time. Published items cannot be moved this way. Check the new slot or reopen the post to confirm the change. If Calendar rejects the move, read its message and choose a future time.

Publish and check delivery

Choose Publish now when every destination is ready, or schedule the post for later. Open the post in Publications and check its destination cards. A published destination can link to the post on its provider; a failed one shows a reason and, when retry is available, a Retry action. Fix the cause first. If LinkedIn published but X failed, fix the X error and retry X. Do not create another post to resend both.

After delivery, use Inbox for supported comments and messages, and Analytics for performance. A blank measurement does not mean publishing failed.

On this page