Publishing
The Publish Panel lets you send, schedule, or manually log generated posts from Content Forge and Video Forge. No copy-paste, no leaving the platform.
Requirements
A connected account for the target platform; see My Account > Social Connections
The profile must be marked as Publish in My Account > Social Connections
If your org has the Approval Workflow enabled, posts route through approval before publishing
Manual logging does not require an active OAuth profile. It records that you already posted the item elsewhere.
Who can send immediately
Owners/Admins manage the connections and decide which profiles are publishable
If approval workflow is off, any user can publish through an already-connected publishable profile
If approval workflow is on, whether a user can send immediately depends on the configured minimum approver role
Publish, schedule, or log
After generating in Content Forge or Video Forge:
Open the Publish Panel on the output card
Pick the platform and connected profile when publishing or scheduling
Edit the final text if needed
Optionally attach media (images or videos)
Choose Post now, Schedule post, or Already posted it yourself
Submit
Scheduled posts appear on the Calendar and publish automatically at the specified time via a background job.
If you post manually outside TheContentForge, the next analytics sync can fetch or match it. You can also log it manually from the Publish Panel after generating in either studio so it appears on the Calendar immediately.
Media attachments
Click the attach button below the textarea to pick an image or video
Uploads run on submit, not when you pick the file, so nothing is uploaded unnecessarily
If a submit fails, the retry reuses the already-uploaded asset; you do not re-upload
Attached media is stored privately, scoped to your org, and shared only at publish time
Ephemeral uploads are cleaned up 24 hours after the post publishes
Threads (X)
When Content Forge returns an X thread (Thread mode or Summarize the project), the Publish Panel switches to a per-tweet editor. Every tweet in the thread is available for all orgs, not just Web3 projects.
Edit each tweet in place - edits are preserved while the Publish Panel is open and never reverted by background re-renders
Add or remove tweets with the + Add tweet / trash buttons
Each tweet has its own media controls:
Attach - upload an image or video for that specific tweet
Generate - create a headline image for that tweet with AI
Brand asset - (Web3 Project orgs) pick a logo, icon, template, or any asset you marked Safe for content in the Asset Library
On submit, the panel creates one scheduled post per tweet, grouped as a single thread and kept in order
Publishing chains the replies natively on X; if any tweet in the chain fails, later tweets do not publish
Instagram and Facebook receive a single concatenated post (thread semantics do not apply on those platforms) with the first tweet's media attached
Platform specifics:
X - images and video are supported on posts and on each tweet of a thread
Facebook and Instagram - image and video posts are planned
Note: X is the only live publishing integration today. Facebook and Instagram are coming soon, so the Instagram/Facebook details above describe planned behavior.
Attach to Experiment
The Publish Panel has a collapsible Attach to experiment section. Expand it to pick one of your active or draft Experiments and assign the post to a specific variant. The experiment list is filtered to the platform you're publishing on, so you only see experiments that can actually receive the post.
Attaching a draft, scheduled, or post-time publish all work - the attachment is created when the post saves
Once published, the post is auto-linked back to the experiment, so you do not need to reattach after publishing
Posts without an attachment are unaffected - the section is fully optional
Approval workflow
When approval is enabled in Settings:
A scheduled or publish-now post enters an Approval pending state
A user at or above the configured min role (Editor, Admin, or Owner) approves or rejects it from the Calendar
Approved posts move to Queued and publish at the scheduled time
Rejected posts are marked accordingly and do not send
Failure handling
If a publish attempt fails (platform error, expired token, media rejected), the event's status flips to Failed and the error message surfaces on the event drawer. Non-fatal warnings, such as a platform caveat after publishing, land in Publish notes so they do not get confused with hard errors.
Related
Content Forge - Where text posts are generated
Video Forge - Where video-derived posts are generated
My Account > Social Connections - Connect accounts to publish through
Calendar - Track scheduled, pending, manual, and published posts
Last updated
Was this helpful?