Skip to main content

Publish Now

Publish Now sends a piece of content to a connected platform immediately. No scheduling, no queue -- it posts and returns confirmation.

From the UI​

  1. Open the content in the editor
  2. Click Publish in the action bar
  3. Select the connection (platform and account)
  4. Click Post

The status indicator shows the post going out. On success, the content status changes to published and the post record is created in the database.

From MCP​

{
  "tool": "publish_now",
  "arguments": {
    "contentId": "content_abc123",
    "platform": "linkedin",
    "connectionId": "conn_xyz789"
  }
}

The tool returns the published post ID and the external platform post ID.

What happens on publish​

  1. Reactor fetches the content text
  2. Reactor looks up the connection credentials for the platform
  3. The content is sent to the platform API
  4. A scheduledPosts record is created with status: 'published'
  5. The content status is updated to published
  6. Any UTM tracking parameters are appended if configured

Platform behavior on publish​

X: Posts as a tweet. Long-form content is truncated to 280 characters. Reactor recommends writing X content to the character limit in the brief.

LinkedIn: Posts as a LinkedIn post. Supports longer text. Line breaks are preserved.

Discord: Posts as a message to the configured channel.

Webflow: Creates a draft CMS item and optionally publishes it. Requires a collection to be configured in the connection.

Ghost: Creates a published post. Title is taken from the content heading if present, otherwise generated from the first line.

Error handling​

If the platform API returns an error, Reactor records the failure in the scheduledPosts table with status: 'failed' and a reason field. You can retry from the content editor.

Common errors:

  • 401 Unauthorized -- Token expired, reconnect in Settings > Connections
  • 403 Forbidden -- Account lacks permission (e.g., LinkedIn page posting requires page admin)
  • 429 Too Many Requests -- Rate limited, try again in a few minutes