What the connection does
The connection holds your Ghost site URL, an Admin API key in its `id:secret` form, and whether a post should arrive published or as a draft. Publishing an approved article creates a post; publishing it again updates that post.
Ghost accepts the article more completely than the other targets. The body is sent as HTML, the cover becomes the post's feature image rather than travelling inside the body, and the meta title and meta description you edited are set as Ghost's own SEO fields. The slug is the one you approved and the publication date can be set, so a backdated article keeps its date.
Section images are referenced from the HTML with the alt text you approved, served from PrismDraft's storage.
- Needs: your Ghost site URL and an Admin API key (`id:secret`).
- Sends: title, slug, HTML body, feature image, meta title, meta description, publication date, draft or published.
- Updating an existing post is supported, so republishing never duplicates.
From your website to Ghost
- 01
Your website becomes a project
One address. PrismDraft reads your pages and drafts the project, the audience, the brand voice and the image style, which you edit before saving.
- 02
A topic with a keyword and an intent
Suggestions arrive on a planning board, each with a working title, a primary keyword, a search intent and a cluster. A keyword the project covers is not proposed twice.
- 03
An outline you approve
A heading per section with its job, its keywords and a target length. Free to generate and free to change, and the thing the draft is written against.
- 04
The run, priced first
About 7 credits for 1,200 words and three images, shown before you start. Each section is written against its heading, with an image prompted from the paragraphs beside it and alt text.
- 05
Approve, then publish to Ghost
Review with versions and comments, edit by hand or with AI, then approve. Publishing is only available from the approved state.
What arrives in the post
The fullest of the four targets, field for field.
| Article field | Ghost field | Notes |
|---|---|---|
| Title | title | As approved |
| Slug | slug | Editable before approval |
| Body | html | Sent with `?source=html` |
| Cover image | feature_image | A real field, not inside the body |
| Meta title | meta_title | Written from the finished article, editable |
| Meta description | meta_description | Written from the finished article, editable |
| Publication date | published_at | Keeps a backdated article's date |
| Draft or published | status | Set on the connection |
| Tags | — | Not sent |
Setting it up
In Ghost, go to Settings, then Integrations, and add a custom integration. Copy its Admin API key, which looks like a long hex id, a colon, and a longer hex secret. In PrismDraft, open the project's integrations, choose Ghost, and paste the site URL and the key. Choose published or draft.
Publish one article and open the post in Ghost. The feature image should be set, the meta fields should be filled, and the body should have real headings. Tags are not sent, so if you file posts by tag, add it in Ghost or set a default on the integration's behalf with a Ghost automation.
Questions
Does Ghost get the meta title and description?
Yes — it is the only one of the four CMS targets with real fields for both, and PrismDraft writes them from the finished article. You can edit either before approving.
Where does the cover image go?
Into Ghost's `feature_image` field, so it behaves like any other Ghost post's feature image. The section images stay inside the body HTML.
Are tags sent?
No. A post arrives untagged. If tags matter to your site's navigation, add them in Ghost after publishing or automate it there.
Can I publish as a draft?
Yes, on the connection: every article from that project then arrives as a Ghost draft for a final look. The article is still marked published in PrismDraft.
What about a newsletter send?
PrismDraft creates the post; it does not trigger a Ghost newsletter. Set that up in Ghost, or publish as a draft and send from there.
Is the key safe?
It is stored encrypted and never returned to the browser once saved. Because an Admin API key is powerful, use one dedicated to this integration and delete it if you disconnect.