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 to access platform connections and publishing history.

​

Connected Platforms

​

Setting Up a Connection

Navigate to Publishing in the sidebar. Select the platform you want to connect and follow the credential setup flow for that platform. Each platform uses a different authentication method:

• OAuth — Medium, LinkedIn. You are redirected to the platform to authorize access and returned automatically.
• API key — Ghost, Dev.to, Hashnode, Beehiiv. Generate a key in your 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.

Credentials are encrypted and stored securely using Google Cloud Secret Manager. You do not need to re-enter them after the initial setup. After connecting, test the connection to confirm it is active before your first publish.

​

Managing Connections

The Publishing workspace shows the status of all configured connections. From here 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
• Test connections before relying on them for delivery

Connection health is checked each time you open the Publishing workspace. If a connection has expired or been revoked on the platform side, WriterzRoom surfaces a re-authentication prompt.

​

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

Content scheduled for a future publish date executes automatically on a 5-minute poll cycle. Set a scheduled date in the publishing options to defer delivery without manual intervention.

​

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 — Publishing integrations are available on Professional and Enterprise plans. Confirm your plan includes the platforms you need.

​

Publishing and Workspace

On Enterprise, publishing connections are shared across the team workspace. Any Editor or Admin can publish to a connected platform. Viewer accounts cannot initiate publishing. See Workspace for team access controls.

​

Related Pages