Content and posting

Schedule, approve, and publish founder-led posts

Scheduling a post and publishing it take different permissions. An agent can fill the queue all week, but a post publishes only once it is approved, and the approval binds to the exact text.

try
Start freeRead the docs

Founder-led content fails on process, not on talent. Posts get written in a doc, pasted into a scheduler, approved somewhere in chat, and a month later nobody can say which version went out or why Tuesday's never did. This is the delivery engine for that work: the queue, the approval, the dispatch, and the attempt history.

The safety property is the part worth buying. Creating or scheduling writes nothing to the platform, and a workflow's create step strips any approval field it is given. A cron job or a workflow can fill a week of drafts, and none of them goes out until it is approved.

Example searches

Ask for it the way you'd say it

Each example is a request in plain words, with what it returns underneath.

  • Fill next week from what you know

    draft five posts for next week from our positioning and the objections we keep hearing

    Drafting is grounded in the workspace wiki and lands in the approval queue rather than on the feed.

  • Approve the week in one sitting

    show me everything scheduled in the next seven days that still needs sign-off

    The queue lists each post with its sender, publish time, and state, and approval binds to the exact text shown.

  • Explain a post that never went out

    why did tuesday's post fail and can it still be retried

    Attempts are recorded individually, not just the final state, so a failure names the sender, the error, and the retry.

Plays

Three motions you can run this week

Each one is a chain of OXYGEN primitives — the same hosted objects your workspace already has, composed.

  • A calendar an agent can fill

    Next week's drafts exist by Friday, written from your own positioning rather than from a generic prompt.

    1. Knowledge Graph
    2. Posts
    3. Publishing
    1. 1Point the drafting step at the pages that hold your voice, offers, and proof.
    2. 2Create them in the queue without the approval flag, so they wait there until someone approves them.
    oxygen publishing posts create

  • Batch the approvals, not the writing

    One review session releases a week of content, and every release is attributable to a person.

    1. Posts
    2. Publishing
    3. Observability
    1. 1Work the queue by publish time and edit in place where the copy needs it.
    2. 2Approve what is ready; an edit after approval cuts a revision and revokes it.
    oxygen publishing posts approve

  • Turn engagement into conversation

    The people who reacted to a post become a warm list instead of a vanity number.

    1. Posts
    2. Signals
    3. Sequences
    1. 1Read the reactors and commenters on an owned post as a deduplicated people list.
    2. 2Enroll them into a capped sequence that references the post they engaged with.
    oxygen engagement engagers

Capabilities

What you get

  • Only an approval releases a post

    A post a workflow creates waits for approval. A workflow may draft, schedule, edit, and cancel, but only an approval releases a post, and a CLI or MCP approval flag counts as one. Your chat with an Oxygent, OXYGEN's in-app AI agent, starts on Auto-approve, which can approve a post; switch it to Ask for approval to review each one.

  • Approval bound to exact content

    Edit an approved post and the approval is revoked, with a recoverable pre-edit revision cut automatically. Nothing publishes in a version that was never approved.

  • An attempt ledger, not a status

    Each publish attempt is stored with its sender, timing, and provider error. A failed post explains itself instead of sitting in a red state with no history.

  • Analytics without a provider call

    The analytics view reads stored snapshots, so opening it spends nothing and shows every owned post recorded here, including ones written directly on the platform.

Boundaries

What Publishing does not own

Publishing delivers; it does not own the artifact. The post, its revisions, and its engagement telemetry belong to Posts. One-to-one outreach is Sequences, a reply in a thread is Messages, and a reaction on a post is a Signal rather than a conversation.

Data sources

Data sources and CRM connections

  • LinkedIn

    The connected account that actually publishes, and the identity a reader sees against the post.

  • Professional Network Data

    Public post and profile reads for research and engager lists, without connecting a second account.

  • Br

    Bright Data

    Scraping infrastructure for the public pages behind a content idea, feeding the draft rather than the dispatch.

Use managed credits where available, or connect a supported provider key on an eligible paid plan. Your provider bills its calls; OXYGEN adds a per-call platform fee. Signed-in CRM connections such as HubSpot have no per-call fee. Connected sending accounts reserve monthly credits. See pricing and supported integrations.

Limits

Where this stops

  • A workflow can schedule but never approve, so a pipeline built from workflows still needs someone working the approval queue.
  • Deleting a post here removes local state and settled history. It does not reach into the platform to unpublish something already live, and the copy stays honest about that.

FAQ

Questions people ask first

Can an automation publish without me?
Not from a workflow. Its create step forces the needs-approval state and discards any approval field, so a cron job or a bug in one cannot release a post. A CLI or MCP call can create a post already approved, and OXYGEN trusts that flag. An Oxygent chat on Auto-approve can approve one, and so can an Agent, a workspace AI worker you configure, with Full access, even on a schedule. Keep the chat on Ask for approval and the Agent's tool access on Ask before changes to review each post yourself.
What exactly does approval bind to?
The exact content that was approved. Any later update atomically cuts a recoverable pre-edit revision and revokes the approval, so the thing that publishes is always the version that was approved.
Which channels can it publish to?
LinkedIn natively, including mention resolution that blocks approval when an identity cannot be verified. Other networks dispatch through a connected delivery integration on the same approval-gated path.
What happens when a publish fails?
The attempt is recorded with its error and the post moves to a state you can retry or cancel. After dispatch, state reflects what the channel says rather than what the scheduler hoped.
Does opening the queue cost credits?
No. Listing, reading, approving, and the analytics view draw no credits. Credits are drawn by the AI steps here, drafting a post and the optional AI review, each under its own credit ceiling.
Can I schedule from a workflow?
Yes. A cron workflow is the recurrence model, so there is no second scheduling concept to learn. It creates posts through the same gated surface and leaves them in the approval queue.

Run schedule, approve, and publish founder-led posts on your own workspace

Sign up, get a working workspace with a one-time credit grant, and run the first play from the web app, the CLI, or your AI assistant over MCP.

Start freeSee pricing