Connect a site
1
Create a custom integration in Ghost
In Ghost Admin, go to Settings → Advanced → Integrations and click Add custom integration. Name it something recognizable, such as
Weelkit.2
Copy the Admin API key
Copy the integration’s Admin API key. It has the form
id:secret — a hex id and a hex secret joined by a colon. Copy the whole value.3
Enter the site URL and key in Weelkit
In Weelkit, open Organization settings → CMS, choose Connect CMS, and choose Ghost. Enter your Site URL and paste the Admin API key, then choose Connect.
4
Weelkit validates the connection
Weelkit checks the key’s
id:secret shape before sending anything, so a mis-pasted key fails straight away. Then it confirms the key can sign in to your site’s Admin API, and shows your site’s title.5
Map, set defaults and verify
Choose posts or pages, review and save the field mapping, set the publishing defaults, and choose Verify test draft: the same flow as every schema-backed destination in the publishing overview.
Discovered schema
Weelkit discovers posts and pages with these fields:
Choose either posts or pages as the primary publishing type. Weelkit fetches tag and author options because those fields explicitly reference Ghost’s tag and user resources. The unselected post/page type is not silently converted into a reference source.
Mapped values must meet the discovered field limits. Plain feature-image captions keep literal text; intentionally mapped HTML keeps its markup.
Draft and publish
The publishing defaults’ Default status decides whether the editor’s button sends a draft or publishes immediately. Start with drafts (see Testing integrations) and switch to publishing once a draft has been verified end to end. The article body uses an HTML card to preserve its markup. Inline images keep their source URLs, so those URLs must stay available. The mapped feature image has a separate upload and field result.Updates to an existing post
When an article is sent again, the publishing default When the article already exists decides what happens: Always update existing updates the same Ghost post, Always create a new item creates another, and Ask before updating asks you to confirm. Choose Update article to update the existing post, or Cancel to leave it unchanged. See Send to your CMS. An update sends the saved article version prepared for that request. Ghost’s revision check prevents a concurrent edit from being silently overwritten. Review any conflict before sending again. Mapped tags and authors replace their previous selections rather than adding to them.Status and address
Weelkit keeps each article’s status in step with its Ghost post. A published post makes the article Published. A draft, scheduled or email-only (sent) post makes it Draft, and so does a post deleted from Ghost. The post’s public URL becomes the article’s address once it’s live. See After you send.Replace the key
If Ghost needs fresh authorization, choose Reconnect and enter the new Admin API key for the same site. Weelkit validates it before replacing the saved credentials; the connection’s mapping and published links stay attached to that site. To rotate a working key, regenerate it in Ghost Admin, then choose Test connection in Weelkit. When the old key is rejected, Reconnect becomes available. Delete an old custom integration only after the replacement works. Disconnect removes the saved setup and is not needed just to reauthorize the same site.When the Admin API is unavailable
If the Ghost Admin API can’t be reached or returns an error, Weelkit shows the result. If Ghost may already have received the post, the outcome stays unconfirmed. Choose Check original CMS send in the editor before sending again; that check does not create another post.Weelkit never exposes Ghost credentials or raw Ghost error bodies. Admin API keys are stored encrypted and never displayed after entry, and Ghost’s error responses are summarized into Weelkit’s own error categories rather than shown verbatim.