Notion
Publish articles to a Notion collection with a cover and formatted content. Drafts stay in Hoxigen until publication.
What connecting it does
Connect with Notion using its own sign-in screen, granting only your blog and article database. Hoxigen stores the login securely; choosing a published collection and saving activates publishing.
Article titles, page content and covers are handled automatically. Excerpt and publication-date fields are optional. Save reserves a Hoxigen ID field so retries can find an article after a lost response instead of creating another.
Publish your parent blog in Notion once. Articles created in that public collection inherit its visibility; Hoxigen drafts remain in its own review queue until publication.
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.
- 1Prepare your blog
In Notion, create a page with an article database. Open Share, then Publish on the blog page and check the collection is public.
- 2Connect with Notion
Sign in and select only your blog page and its article collection. No API key is needed.
- 3Choose your collection
Select the article collection. The title, page body and cover are handled automatically; excerpt and date fields are optional.
- 4Verify and save
Select Verify connection, then Save. New articles inherit the collection's public visibility. Hoxigen adds an ID field to prevent duplicate posts.
What actually gets published
Field by field, so nothing arrives as a surprise.
Headings, paragraphs, lists, links, tables, quotes and emphasis are converted from the reviewed article into Notion page content. Your Notion layout controls the appearance; website CSS is not copied.
The cover is uploaded to Notion, up to 5 MB. Inline images reference their public source URLs, which must stay reachable.
Choose an excerpt text field and publication-date field when your collection has them. Notion controls page URLs and SEO settings; no custom slug or JSON-LD is inserted.
What happens when an article is refreshed
Refresh the same Notion article
Hoxigen re-reads the article before writing and refuses a refresh when the live page changed since the draft was prepared. Confirmed update steps have durable receipts; an uncertain write requires checking the page before retrying.
Refresh keeps the page URL, original publication date and unrelated properties. Omitting a new cover preserves the existing image. Notion has no atomic compare-and-set for these writes; avoid editing the same page while it is publishing.
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.
Hoxigen cannot turn a private Notion site public through the API. Publish the parent blog and verify the collection is public. A draft-status filter does not make individual pages private.
Refresh refuses unsupported or truncated content, including child pages, embeds, synced blocks and callouts, rather than silently deleting it. Notion controls typography and layout.
The connection publishes to the collection you select. It does not generate a blog layout, send newsletters, change public visibility or synchronize manual edits in real time.
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 access against the real API before you save its publishing destination. OAuth sign-in stores the login first; choosing a collection and saving finishes the connection.
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.
- Ghost
Publishes articles to your Ghost publication with a custom integration, including cover and inline images, and refreshes the same post.
- Framer
Publishes articles into your Framer CMS collection, uploads cover and inline images, and refreshes the same article.
- 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 Notion when you like what you read — nothing publishes before that.