Connect the one you publish on
A publishing connection belongs to a project, not to your account, so an agency keeps one per client and an article can only reach the site its project belongs to. Every credential is stored encrypted and never returned to the browser after it is saved. Publishing is available only from the approved state; the one deliberate exception is a publishing plan whose Autopilot you switched on, which writes, approves and publishes that plan's entries on their day up to its credit cap.
Republishing an article updates the post or item it created rather than making a duplicate, which is what makes a correction safe and also what makes an edit you only made in the CMS replaceable. Decide early which side is the final home.
The four connectors differ in how much of an article they can carry. Ghost takes the most: a real feature image field and both SEO meta fields. Webflow takes five collection fields. WordPress takes the body, the slug and the excerpt, with the cover inside the HTML, because its REST API exposes no featured-image field to this integration. Shopify takes the body, the handle, the summary and an image, and always arrives published.
Where none of them fits, there is a signed outbound webhook: PrismDraft posts the article to a URL you control with a signature you verify, and you create whatever your system needs. The webhook catalogue and the signature scheme are documented in the API reference, along with a typed SDK.
Questions
Which integration carries the most of an article?
Ghost. It has real fields for the feature image, the meta title and the meta description, so almost nothing has to be re-entered. WordPress and Shopify take the description as an excerpt or summary; neither takes a meta title.
Do any of them publish without approval?
Not on their own. Publishing is only available on an approved article. A publishing plan with Autopilot on is the single exception, and it is off unless you switch it on for that plan.
Are my images copied into the CMS?
No. Images are generated, resized, stripped of metadata and compressed by PrismDraft and served from its storage; the published post references them by URL. Moving off PrismDraft means rehosting them.
Can one article go to two places?
A project has one connection, so an article has one target. For two, use the signed webhook and fan it out yourself, or keep a project per destination.
What if my platform is not here?
Use the signed webhook, or the REST API and the typed SDK, and create the post yourself. There is no half-supported connector: a target is either implemented and documented here or it is not offered.