Ghost
Create a custom integration in Ghost Admin, copy its API URL and Admin API key, and verify the connection in Hoxigen.
What connecting it does
Hoxigen connects directly to your publication's Ghost Admin API. You create the integration in your own Ghost settings and can revoke it there. Verification reads an authenticated article resource before the connection is saved; it creates no test post.
Publishing first creates a remote draft and records its Ghost post ID, then publishes that same post on your website. A retry uses the recorded ID. If Ghost's draft-creation response is lost, Hoxigen stops for you to check the publication instead of blindly creating another post.
The body is sent as a Ghost HTML card so its formatting, image captions and right-to-left text survive. You can edit that card's HTML in Ghost; the body is not converted into separate native editor blocks.
What it needs from you
The same steps the connect screen walks you through, so you can see the whole of it before you sign up for anything.
- 1Open Integrations
Sign in to your publication's Ghost Admin. Open Settings, then Advanced, then Integrations.
- 2Create a custom integration
Select Add custom integration, enter Hoxigen in Name, then select Add.
- 3Copy the API credentials
In the integration, copy API URL and Admin API key. The Content API key cannot publish articles.
- 4Verify and save
In Hoxigen's Ghost connector window, paste both values, select Verify connection, then Save.
What actually gets published
Field by field, so nothing arrives as a surprise.
Title, slug and the article body become a published Ghost post. Ghost returns the post's URL, which Hoxigen keeps with the article.
The featured image becomes the cover, with the article title as its alt text. Images, alt text and captions inside the article remain in its HTML card. The images use Hoxigen's public media URLs.
New posts receive the article tags, title as the meta title, and meta description. Refreshes keep the post's existing tags and author relationships.
What happens when an article is refreshed
Yes — the same Ghost post, at its existing URL.
Hoxigen reads the published post at the target URL and records its current title, body and update timestamp. Before writing a refresh it compares that version again.
If someone changed the post in Ghost, Hoxigen refuses the update as a conflict. Ghost also checks the update timestamp when the write arrives, protecting edits made between the read and the update.
A successful refresh updates the title, body and metadata without changing the slug, publication status or author relationships. A refresh with no new cover keeps the existing one.
Refreshing an article rather than writing a new one is how a page that used to rank keeps ranking.
What it cannot do
You would find these out in week two anyway. Here they are in week zero.
The connector publishes posts. It does not send newsletters, create pages, manage members or alter paid subscriptions.
A Content API key can read public content but cannot publish. Your publication must allow custom integrations and expose its Admin API at a reachable HTTPS API URL.
A post published on a private or pre-launch Ghost site remains behind that site's access screen. Connecting Hoxigen does not change the publication's privacy settings.
The connector references public image URLs instead of copying the files into Ghost's media storage. Those URLs need to stay reachable for images to appear.
Everything on this page describes what the connector does today. Found something that does not match what you see in the product? hello@hoxigen.app — we will correct the page.
How publishing works, whichever you pick
Drafts land in your queue with their images, meta description, a short FAQ and internal links. You can edit, approve or reject each one. Ignore the queue and it publishes on schedule anyway — that is the point of an autopilot. Prefer to sign off first? Set the connector to Approve first.
Connect two blogs and each gets its own article per publishing slot, written for it. Hoxigen does not syndicate one body to several sites and hope search engines pick a winner.
Each connector verifies its credentials against the real API — a signed test request, a token exchange, a collection read — before Hoxigen saves anything. A connector that cannot publish says so on the day you connect it, not on the day you expected an article.
A publish that fails keeps the reason on the article and tries again, up to three times. If it still fails, it stops and tells you, so you can reconnect the site and retry it.
Publishing somewhere else
- WordPress
Our own plugin turns your site into a signed receiver. Articles arrive as posts and refresh at the same permalink.
- Shopify
Publishes to your store's blog through the Admin API, on your own domain, with the product-adjacent content Shopify stores rarely get around to writing.
- Wix
Publishes to your Wix blog with an API key you generate, converting each article into Wix's own rich content format.
- Webflow
Publishes live CMS items into the blog collection you choose, mapping your existing fields instead of demanding new ones.
- Any site, by signed webhook
One signed HTTP POST per article to an endpoint you own. Next.js, Rails, Astro, Django, a static build — if it can receive JSON, it can receive articles.
Give it your URL. See what it drafts.
Connect Ghost when you like what you read — nothing publishes before that.