Publishing

Publishing is the final step in the content lifecycle, moving a finalized draft from your Content Library to an external platform. WriterzRoom supports direct publishing to seven platforms without leaving the product. Navigate to Publishing in the left sidebar for job history, or Settings → Publishing (also reachable from Integrations) to connect or manage platform credentials.

​

Connected Platforms

​

Setting Up a Connection

Navigate to Settings → Publishing. Select the platform you want to connect and follow the credential setup flow for that platform. The same connection screen is also reachable from Integrations. Each platform uses a different credential type:

• Integration or OAuth token — Medium and LinkedIn. Generate the token in the platform’s own developer or account settings, then paste it into WriterzRoom. WriterzRoom does not currently run a redirect-based OAuth consent flow.
• API key — Ghost, Dev.to, Hashnode, and Beehiiv. Generate a key in the platform dashboard and paste it into the connection form.
• Application password — WordPress. Generate one from your WordPress dashboard under Users → Security → Application Passwords. Do not use your login password.

Sensitive credential fields are encrypted before they are stored in the application database. Production supplies the field-encryption key through Google Cloud Secret Manager. WriterzRoom never returns the stored secret values to the browser. The connection form validates credentials before saving them.

​

Managing Connections

The Publishing page itself shows a connected-platforms glance — which of the seven destinations are connected at a look — alongside job history; it links into Settings → Publishing rather than hosting connection forms directly. From Settings → Publishing (or Integrations, which shares the same connection screen) you can:

• See which platforms are connected and healthy
• Re-authenticate when credentials expire (OAuth tokens, rotated API keys)
• Disconnect platforms you no longer use
• Switch between a card and a list layout as the platform catalog grows

The connected list reports saved, active credential records; it does not make a live request to every destination when the page opens. A revoked or expired credential is surfaced when validation or publishing fails, at which point reconnect the platform with a current token or key.

​

Publishing History

Below the connected-platforms glance, the Publishing page lists every publishing job with its platform, status, and timing, filterable by platform and by status (pending, published, partial, failed). Each job supports:

• View post — opens the delivered content on the destination, when available
• Retry — re-attempts only the platforms that failed within that job, not the ones that already succeeded
• Disconnect — clears a broken or revoked credential directly from a failed job, without a trip to Settings
• Remove from history — clears the record only; it does not unpublish anything already live, and is unavailable while a job is still in progress

​

Publishing a Draft

​

Tracking Published Content

Content cards in the library show a Published badge for pieces with completed publishing jobs. The content detail page shows a Published Links card listing the platform URLs where the piece has been delivered, including publish date and platform name.

​

Scheduled Publishing

User-facing scheduled publishing is not currently available. The backend includes a protected five-minute executor for scheduled jobs, but the product does not yet expose the creation and management workflow required to use it safely. Publish immediately or create a destination draft, then schedule from the destination platform when supported.

​

Platform-Specific Notes

Medium — Content is published as a draft by default. You can choose to publish immediately, but Medium’s distribution algorithm favors content that is reviewed before going live. WordPress — Requires an application password, not your login password. Generate one from your WordPress dashboard under Users → Security → Application Passwords. LinkedIn — OAuth tokens expire periodically. If publishing fails after a period of inactivity, re-authenticate from the Publishing workspace. Beehiiv — Requires both an API key and a publication ID. The publication ID is found in your Beehiiv dashboard under Settings → General. Ghost — Requires a Ghost Admin API key. Generate one from Ghost Admin → Integrations → Add custom integration.

​

Troubleshooting

Connection errors — Re-authenticate via the Publishing settings if credentials have expired. OAuth tokens (Medium, LinkedIn) expire after extended inactivity. Publishing failures — Check the destination platform’s rate limits and content policies. Some platforms reject content that exceeds length limits or contains unsupported formatting. Format issues — WriterzRoom publishes in the format most compatible with each platform: Markdown for Medium, Dev.to, Hashnode, and Ghost; HTML for WordPress, LinkedIn, and Beehiiv. If formatting appears broken on the destination, check the platform’s Markdown or HTML rendering rules. Missing platforms — Refresh the connection catalog and confirm that the destination is one of the seven adapters above. Substack is available as a writing profile but has no direct publishing adapter because it does not expose the required public publishing API.

​

Publishing and Workspace

Publishing credentials, jobs, and destination history are personal to the signed-in account. Organization membership does not share a connection with other members, and workspace roles do not grant access to another member’s publishing credentials. See Workspace for the current team boundary.

​

Related Pages