Content and posting
Schedule, approve, and publish founder-led posts
A publish time is not permission. 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. In the web editor, Schedule and Post Now approve as they save.
Founder-led content fails on process, not talent. Posts get written in a doc, pasted into a scheduler and approved in chat, and a month later nobody knows which version went out. This is social publishing built for that work: the queue, the approval, the dispatch, and the attempt history.
The safety property is the part worth buying. A post saved without approval sends nothing, even after its publish time passes. A scheduled workflow can fill a week of drafts that wait for approval, unless one of its own steps approves them.
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 page and hold them for review
The drafts start from your pinned voice, brand, and positioning pages, and none reaches the feed until it is approved.
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.
Explain a post that never went out
why did tuesday's post fail and can it still be retried
Each attempt is recorded, so a failure names the sender and the error, and whether it can be retried.
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, not a generic prompt.
- 1Pin your voice and positioning pages, then approve the pin proposals. Every post draft starts from them, and its topic carries the offer or proof.
- 2Create them without the approval flag, so they wait in the queue for review.
oxygen publishing posts createBatch the approvals, not the writing
One review session releases a week of content, not approvals scattered across chat.
- 1Work the queue by publish time and edit in place where the copy needs it.
- 2Approve what is ready; changing the copy after approval saves a revision and revokes it.
oxygen publishing posts approveTurn engagement into conversation
The people who reacted to a post become a warm list instead of a vanity number.
- 1Read the reactors and commenters on an owned post as a deduplicated people list.
- 2Enroll them into a sequence whose first message mentions the post they engaged with.
oxygen engagement engagers
Capabilities
What you get
Only an approval releases a post
A workflow's post step saves posts unapproved unless it sets the approval flag, and a step that calls the approve tool approves them. So does a call from the command line (CLI) or an AI assistant over MCP with the approval flag. Your workspace's shared Oxygent chat (OXYGEN's in-app AI agent) starts you on Auto-approve.
Approval bound to exact content
Change an approved post's copy, media or LinkedIn sender and the approval is revoked. A copy or media edit first saves a recoverable pre-edit revision.
An attempt ledger, not a status
Each publish attempt is stored with its sender, timing, and provider error, so a failed post explains itself.
Analytics without a provider call
The analytics view reads stored snapshots, so opening it spends nothing. It covers your LinkedIn and X posts, including recent ones written directly there, but not Instagram, TikTok, Facebook or YouTube.
Boundaries
What Publishing does not own
Publishing delivers; Posts owns the post, its revisions, and its engagement. Net-new outreach is Sequences, even to one person, and a reply in a thread or a single direct email is Messages.
Data sources
Data sources and CRM connections
LinkedInThe 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.
- BrBright Data
Reads public LinkedIn posts from a post, profile, or company page link, for research before you write, not for publishing.
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 LinkedIn account publishes up to 10 posts a day, or up to 25 if you raise its limit. A post over the limit waits, and one held more than 24 hours past its time fails.
- Deleting a post removes only OXYGEN's copy; a live post stays on the channel until you remove it there.
- Posts go out from an account you connect, and connecting one needs a paid plan. On Free you can still write and queue posts.
FAQ
Questions people ask first
Can an automation publish without me?
What exactly does approval bind to?
Which channels can it publish to?
What happens when a publish fails?
Does opening the queue cost credits?
Can I schedule from a workflow?
Try Publishing in your own workspace
Sign up free with a one-time credit grant, and an in-app AI agent researches your company and proposes your first plays. Pick a plan to run one from the web app, the command line, or an AI assistant you link over MCP.