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. Open Publishing for job history, and Integrations to connect or manage platform credentials. The publishing-destinations link in Settings also opens Integrations.

​

Connected Platforms

​

Setting Up a Connection

Open Integrations, select the platform, and follow its credential setup flow. Settings’ publishing-destinations link leads to this same connection manager. 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 shows a summary of the seven destinations’ saved connection records alongside job history. It directs connection management to Integrations, where 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
• Scan connections in the list layout, which is the default, or switch to cards

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, held). Held means a release policy stopped the job, such as an approval that has not been given or a source that was revoked; nothing failed, and the job names the reason. Each job supports:

• View post — opens the delivered content on the destination, when available
• Retry — re-attempts only the platforms that failed or were held within that job, not the ones that already succeeded. Retry a held job once the approval or source check it names is satisfied
• 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. Enter the site URL as its public https:// (or http://) address; see Site URL requirements. 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. The site URL follows the same requirements as WordPress.

​

Site URL requirements

WordPress and Ghost are reached at the address you enter, so WriterzRoom checks that address before contacting it, when you connect and again before every publish:

• It must start with https:// or http:// and use the standard port (443 or 80).
• It must not include a username or password.
• Its host must resolve only to public internet addresses. Loopback, private-network, link-local, cloud-metadata and other reserved addresses are refused, including hostnames that resolve to them.

A refused address is reported as site URL refused with the rule it broke, and nothing is sent to it. Publishing requests do not follow redirects, so enter the address your site actually serves, including www. if your site redirects to it. When a destination rejects a publish, the job records the HTTP status and a short excerpt of the destination’s error response.

​

Troubleshooting

Connection errors — Re-authenticate via the Publishing settings if credentials have expired. OAuth tokens (Medium, LinkedIn) expire after extended inactivity. A site URL refused error means the WordPress or Ghost address failed the site URL requirements; re-enter the site’s public address. 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