PostOnce.co
Log in Start 14-day Pro trial
Log in Start 14-day Pro trial

Content scheduling.
One complete workflow.

Bring in an article or draft, write the right version for each audience, and schedule your connected channels. Track every result from the same workspace, with API and MCP access on paid Pro and Agency plans.

Start 14-day Pro trial →Explore API & MCP
01Compose

Article · Image · Short video · Long video

One source
02Control

Variants · Role checks · Scheduling · Drafts

Validated
03Deliver

Queues · Rate limits · Retries · Receipts

Observable
04Inspect

Campaign · Destination · Attempts · Errors

Reviewable
05Automate

REST API · Local + hosted MCP · Signed source workflows

Scoped

Illustrative sample workspace

The interface keeps the whole decision visible.

Source, destination variants, queue health, and delivery history share one campaign context. Preview-only surfaces say so in the app.

Workspace / Northstar Studio

Illustrative product preview
P
NS

New content

Compose once

Save draft
ArticleImageShort videoLong video

The durable distribution playbook

Full article + four destination-specific social teasers

Destinations 6 selected

Edit per channel
WWordPressGGhost✦BlueskyMMastodonTTelegramDDiscord
14 Beta · not self-service5 Approval required
ScheduleToday · 4:30 PM
Review 6 deliveries →

Delivery

Publish queue

Illustrative
✦

BlueskyPublished · just now

✓
W

WordPressPublished · 1 min ago

✓
M

MastodonQueued · next delivery

T

TelegramRetry 2/3 · in 4 min

Retry now

Delivery rate

5/6
Illustrative workspace data
01 / Compose

Four formats.
One durable source.

Start from writing or attach stored media, then keep the source and destination copy in one campaign.

  • Article, post, and video content types
  • Direct-to-storage media uploads
  • Destination compatibility shown before selection
  • Drafts and explicit timezone scheduling
02 / Adapt

Shared idea.
Destination copy.

Use the source as a starting point, then write a deliberate override for each selected destination.

  • Per-destination content overrides
  • Workspace voice and terminology guidance
  • Blocked terms checked before delivery
  • One master remains easy to recover
03 / Product preview

Approval design,
labelled honestly.

This is a preview of multi-step team approval routing. API and MCP publish plans already have a separate, enforced browser review; the team workflow shown here is not a live entitlement.

  • Current role checks protect edits and administration
  • Approval decisions and comments are preview-only
  • Keep sensitive routes manual today
  • Status will change only after regression-tested enforcement
04 / Deliver

Retry safely.
Resolve clearly.

Temporary API problems should not become duplicate public posts. PostOnce.co retries rate limits and known-idempotent failures, while ambiguous outcomes stop for review.

  • Leased queue with heartbeat and backoff
  • Per-destination attempt records
  • Cancel before a delivery completes
  • Automatic retries never consume publish quota
05 / Inspect

Operations first.
Sample outcomes second.

Destination state, attempts, errors, and published URLs are persisted today. Engagement metrics remain an illustrative preview until approved connectors can retrieve them.

  • Campaign and destination delivery state
  • Attempt timing and failure reasons
  • Published IDs and URLs when returned
  • Example engagement values are labelled

Build the route once. Keep the rules explicit.

Turn trusted inbound events into workflows with signed secrets, strict filters, allow-listed transforms, active destinations, and idempotent event IDs.

The details that shape a real workflow.

01Can each destination have different copy?

Yes. A campaign keeps one source while each selected destination can override its copy. Per-destination media transforms and schedule overrides are not launch-ready yet.

02Can I publish automatically from another system?

Yes. Signed source-webhook workflows accept a strict event, apply allow-listed filters and transforms, and queue delivery to active destinations. Each secret is shown once and can be rotated.

03How do approvals work?

Multi-step team approvals are a product preview. Separately, the API and MCP reviewed-publish flow requires an authorized person to approve an exact publish plan in the browser before it can be consumed. Those are different workflows; team invitations and approval routing are not included as live collaboration features.

04Does PostOnce.co alter uploaded media?

No. The current release keeps the uploaded source in private object storage and does not silently crop or transcode it. Destination compatibility is your responsibility until media transforms ship.

Put the workflow into practice.

Follow the blog-to-social example, then check how to handle each delivery result.

A calmer way to publish everywhere.

Explore the workflow with sample data, or start your 14-day Pro trial. No card required.

Start 14-day Pro trial Try the guided demo