Create one custom app in your Shopify admin, paste its credentials, pick which blog to write to, and articles publish to your store's own domain.
Hoxigen talks to the Shopify Admin GraphQL API as a custom app you created inside your own store. There is no Hoxigen app to install from the Shopify App Store, no OAuth screen, and no third-party organisation in the middle: the credentials are yours, minted in your admin, and you can revoke them there in one click.
The access token is short-lived and minted on demand from your client credentials, which means a rotated secret takes effect immediately rather than leaving a stale token working for a day.
Articles are created on the blog you pick during setup — most stores have the default News blog, and a store with several gets a choice — and are published immediately rather than left as drafts.
The same steps the connect screen walks you through, so you can see the whole of it before you sign up for anything.
At dev.shopify.com, open Apps, click Create app, and name it Hoxigen. It has to be created in the same organization as the store, or the credentials grant will not work.
Under Access, Scopes, select read_content and write_content. Nothing else is needed, and nothing else is asked for — Hoxigen never gets orders, customers or payment data.
Click Release, then open the app's Installs page and install it on your store.
The one ending in .myshopify.com, shown under Settings, Domains.
From the app's Settings, copy the Client ID and Client Secret. Paste all three into Hoxigen, verify, and choose the blog articles should go to.
Field by field, so nothing arrives as a surprise.
Created with the article's slug as its handle and published on the spot, dated with the article's publish time.
The article HTML becomes the body, the meta description becomes Shopify's summary field, and article tags become the article's tags.
Attached by URL with the article title as alt text. An article with no image of its own leaves the image already on a Shopify article untouched.
The byline from your app profile, sent as the article's author.
Yes — the same article, the same handle, so the same URL.
Hoxigen looks the live article up by its handle under your blog, re-reads its current title and body straight from Shopify, and compares that against the version the refresh was drafted from.
Different? Somebody edited it in the Shopify admin, and the update is refused as a conflict instead of clobbering their work. Identical? The article is updated in place — handle untouched, so links, shares and any ranking the URL earned survive.
Publishing is also safe against duplicates in the other direction: if an article with that handle already exists on the blog, Hoxigen adopts it rather than creating a near-identical second one.
Refreshing an article rather than writing a new one is how a page that used to rank keeps ranking. It is rolling out to accounts gradually; publishing new articles is not gated on it.
You would find these out in week two anyway. Here they are in week zero.
This connector carries a Beta pill in the product. It publishes and refreshes articles today, and it is covered by an automated test suite against the platform's API — but it has run on fewer live sites than our webhook pipeline has, and we would rather you knew that before you connected your only blog to it.
Shopify's client-credentials grant only issues tokens when the app and the store share an organization. An app created elsewhere is rejected at verification with that reason spelled out.
Articles go to the blog chosen at setup. Writing to two Shopify blogs at once is not something the connector does.
No product descriptions, no collection copy, no pages. Shopify's blog is the whole surface here.
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.
Drafts land in your queue with their images, meta description, FAQ schema 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.
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.
Connectors are probed on their own schedule. An expired token, a revoked scope or a key that no longer does what publishing needs flips the connector to Reconnect and tells the seats that asked for alerts.
Our own plugin turns your site into a signed receiver. Articles arrive as posts and refresh at the same permalink.
Publishes to your Wix blog with an API key you generate, converting each article into Wix's own rich content format.
Publishes live CMS items into the blog collection you choose, mapping your existing fields instead of demanding new ones.
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.
Connect Shopify when you like what you read — nothing publishes before that.