Website integrations
Connect your website once and Contengi reads what is live, writes new posts in your voice, edits old ones section by section and publishes back to the same URL. Pick your platform.
Pick your platform
Core REST API and an Application Password. No plugin to install.
Setup: About two minutesPrivate Shopify appA private app on your own store with one scope: write_content.
Setup: About five minutesSite API tokenData API v2 with a site token, mapped to your own collection fields.
Setup: About three minutesSigned webhookOne signed endpoint that Claude Code writes for you from a single prompt.
Setup: One prompt to Claude CodeSigned webhookOne route handler that v0 adds to your Next.js app from a single prompt.
Setup: One prompt to v0Astro, SvelteKit or a site your agency built: anything that can answer an HTTPS request uses the signed webhook. Framer, Carrd and other no-backend builders read a private feed of your posts.
How the webhook works| WordPress | Shopify | Webflow | Claude websites | v0 websites | |
|---|---|---|---|---|---|
| Connects with | Application Password | Private Shopify app | Site API token | Signed webhook | Signed webhook |
| Setup | About two minutes | About five minutes | About three minutes | One prompt | One prompt |
| Plugin or code | None | None | None | One endpoint | One route |
| Browse live posts | Posts Contengi published | Posts Contengi published | |||
| Write and publish | |||||
| Edit and republish at the same URL | |||||
| Publish as draft | Publishes live | Your endpoint decides | Your endpoint decides | ||
| Unpublish and delete from Contengi | In WordPress | In Shopify | In Webflow |
FAQ
WordPress, Shopify and Webflow connect natively. Sites built with Claude, v0 or any other code connect through one signed endpoint, and static sites without a backend can pull a feed of published posts instead.
Read the posts that are already live, write new ones in your brand voice, edit them section by section, publish on your say-so and republish changes over the same URL.
Each brand in Contengi connects to one website. Run several brands and each one can have its own site.
No. An update has to find the original post, by the id Contengi saved or the slug in its URL. If it cannot, the publish stops and tells you why, so the old version never stays live beside a new one.
If your site can answer an HTTPS request, use the signed webhook, the same one Claude and v0 sites use. Framer, Carrd and other no-backend builders can read a JSON or RSS feed of your published posts.
Keep exploring