Ghost

Your first draft

Put reviewed copy into a Ghost draft.

Send the finished HTML to Ghost with an explicit draft status. Then open the draft in Ghost Admin to check the content and decide when to publish it.

Connect the intended Ghost site

Create or select a custom integration in Ghost Admin and save its Admin API key in your StackOS connection. Enter the site/admin domain root, such as https://example.com, without /ghost/api/admin/. Keep the key in StackOS. Ghost's Admin API guide explains the connection.

Ask for one draft

This is an illustrative request. Replace the site, title and HTML with your own reviewed copy.

In the connected Ghost site https://example.com, create a draft titled “September product notes” using the HTML below. Set its status to draft. Return the post ID and status from Ghost's response.

The Create Ghost Post action accepts this input:

{
  "source": "html",
  "post": {
    "title": "September product notes",
    "html": "<p>A reviewed summary of the changes in this release.</p>",
    "status": "draft"
  }
}

Set status explicitly. StackOS passes the supplied status to Ghost; it does not always choose draft for you.

Check and finish the same draft

1. Look for the created post in the returned posts array. Save its id and check that status is draft. If those fields are missing or unclear, inspect Ghost Admin before treating creation as complete.
2. Open that draft in Ghost Admin. Check its title, body, links, author, tags and preview. Ghost converts the submitted HTML, so inspect the formatting there.
3. Make your edits and publish that existing draft in Ghost Admin when it is ready. StackOS 2.1.31 exposes a create-post action for Ghost. It does not expose an action to update or publish an existing draft; another create request asks for a new post.

If the result is uncertain

A missing response does not prove that Ghost created nothing. The connector can retry failed requests, so duplicate posts are possible. Inspect Ghost Admin for the intended draft and any duplicates before deciding whether to send another create request.