Wix
Generate a Wix API key with blog access, paste it with your Site ID, and articles publish to your Wix blog as native posts.
What connecting it does
Wix blog posts are not HTML documents — they are Ricos rich-content trees. Hoxigen converts each article through Wix's own conversion API rather than guessing at the format, so headings, lists, links, quotes and images arrive as real Wix blocks that you can keep editing in the Wix editor afterwards.
The featured image is imported into your Wix Media Manager first and waited on until Wix reports it ready, then set as the post's cover, which Wix shows in the blog feed, the post list and social shares. Wix never shows a cover inside the post, so the same image also opens the post body. An image that never finishes importing costs you the image, not the article.
The post is created as a draft and then published in one pass, so a half-written post never appears on your site. Wix needs every post to have an owner, and an API key is not a site member, so Hoxigen credits the member who owns your blog's latest post.
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 API Keys
In Wix, open your account menu, go to Account Settings and click API Keys, or go straight to manage.wix.com/account/api-keys. Then click Generate API Key.
- 2Name it and pick the site
Name the key Hoxigen and select the site you want articles published to.
- 3Set permissions
Under All site permissions, click Show all, then check these three (click any to copy): , , . Blog alone is not enough: the rich-content conversion and the image import each need their own.
- 4Generate and copy the key
Click Generate Key at the top of the page and confirm the verification code Wix sends you. Wix shows the key exactly once. Copy it before you close the dialog.
- 5Find your Site ID
The long UUID in your dashboard address after /dashboard/, also shown under Settings. Paste both into Hoxigen and verify.
What actually gets published
Field by field, so nothing arrives as a surprise.
Created as a draft and published in the same pass, under the article's slug as its SEO slug.
The article body is converted into Wix's Ricos format block by block, so the post stays editable in the Wix editor.
The article's meta description becomes the post excerpt.
Imported into your Media Manager, set as the cover for the feed and social shares, and placed at the top of the post body. A refresh with no new image keeps the cover already on the post.
What happens when an article is refreshed
Yes — the live post is updated and republished, keeping its URL.
Hoxigen finds the post by the slug in the URL, checks the post it found really is the one at that address, and compares its current text against what the refresh was drafted from.
An edit made in the Wix editor since then shows up as a mismatch and the refresh is refused as a conflict. Otherwise the post is patched and republished in place.
This path was run against a live Wix site before the connector left beta: the refreshed post kept its address and its cover image, and the new text replaced the old.
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.
Wix Blog alone is not enough: the conversion to rich content and the image import each need their own permission, and a blog with no posts yet needs Read Members too, to find a member to credit. Verification names whichever one is missing.
Wix issues API keys at the account level and scopes them to sites you select. If that is broader than you want a marketing tool to hold, this is the connector to weigh carefully.
No Wix Stores product pages, no site pages, no galleries.
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 and internal links, plus a short FAQ where readers need one. 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.
- 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.
- Notion
Sign in with Notion and publish formatted articles with covers to your public blog collection.
- 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 Wix when you like what you read — nothing publishes before that.