Publish reviewed articles to Ghost

Prerender Buddy delivers reviewed article text to Ghost as a post. It can save an unpublished draft or publish the approved post after explicit confirmation.

This version accepts supported Markdown or plain-text articles and their title, slug and excerpt. Images, media embeds and newsletter sending are outside this connection. The site owner is used as the default author.

Read Article Generation for the evidence, context and human review that come before delivery.

Create a dedicated custom integration in Ghost Admin's Integrations settings. Copy its Admin API key and admin/API URL. Ghost's custom-integration guide explains where these values come from.

Use the Admin API key, not the read-only Content API key. Treat the Admin API key as a secret.

For Ghost(Pro), the admin address can differ from the custom public domain. Use the integration's admin site root or Admin API URL, including the installation path where applicable. PB requires a public HTTPS address.

1. Open your website in PB Sites, open Publishing and select Ghost.
2. Enter the Ghost admin site URL and dedicated Admin API key.
3. Choose Save destination, then Check connection.
4. Confirm that the connection belongs to the intended Ghost publication before delivering an article.

Saving Ghost replaces another active destination for this PB website. If you change the admin URL, provide the key for that Ghost installation and check the connection again.

Review the full article, verify its claims and supporting links, remove unsupported media, and approve the intended version in PB.

Sending a draft saves an unpublished Ghost post. Confirmed publication saves the article and requests its published state. PB uses a stable article identifier in the generated slug to associate later deliveries with the same post.

A published Ghost post is separate from a sent newsletter. This connection does not send email newsletters or promise delivery to subscribers.

Changes to a published Ghost post can become live immediately. PB blocks a draft action from rewriting or unpublishing an already live post.

To update a live post through PB, review and reapprove the changed article, then explicitly confirm publication. A Ghost post in an unsupported or changed state may require review in Ghost before another delivery.

For a later approved release, use a separate PB publication schedule. An editorial planning date is not a publication instruction.

Check the Ghost post before retrying a timeout or ambiguous delivery. It may already have been saved, even if PB did not receive a complete response.

For authentication failures, confirm the admin URL and Admin API key. For a changed-post conflict, inspect the current Ghost version before another write.

Disconnecting PB does not delete Ghost posts. Revoke or replace the dedicated integration key in Ghost separately when needed.