AI SEO blog for Wix
On Wix the integration is a Velo HTTP Function you add in Dev Mode. It validates a secret header, writes every article language into a Wix CMS collection, imports the cover into Wix Media Manager, and answers Blogent only after all languages are saved.
How to connect Blogent to Wix
Wix
Expose a protected Velo HTTP Function that upserts Blogent articles into a Wix CMS collection.
The workflow receives the standard Blogent JSON contract: publish every language in article, copy the temporary cover into persistent storage, preserve language-specific aliases, and map the optional author fields.
Test connection always sends a real article. Make, n8n, and Wix must return {"posted": true} only after publishing finishes. ApiX-Drive, Albato, and Zapier acknowledge the queued workflow first, so Blogent asks you to verify the run and the resulting article on the destination site.
- Enable Dev Mode, create a Wix CMS collection for articles, and add fields for language, alias, title, preview, rich content, SEO metadata, rubric, image, publish date, reading time, and optional author data.
- In Backend
http-functions.js, implement a POST function, validate a secret request header, parse the JSON body, and process every language underarticle. - Upsert by stable language plus alias, import the temporary cover into Wix Media Manager, store its permanent Wix URL, and expose the collection through the site’s dynamic blog pages.
- Return HTTP 200 JSON
{"posted": true}only after all languages are saved. Publish the Wix site, enter its production/_functions/...URL in Blogent, and run the real connection test.
This integration receives the standard Blogent JSON payload. Review the full contract — fields, HTML tags, response format — and try the live webhook tester.
Webhook tester
Send a test article to your endpoint and check how the CMS processes the data. Edit the JSON if needed.
What you get after connecting Wix
- Articles are upserted by language plus alias, so a repeated delivery updates the existing item instead of duplicating it.
- The temporary cover is imported into Wix Media Manager and stored as a permanent Wix URL.
- The collection is exposed through the site’s dynamic blog pages, so articles use your own design.
- The function returns
{"posted": true}only after every language is saved, so a partial publish is reported as a failure.
Requirements and compatibility
- Platform
- A Wix site with Dev Mode (Velo) enabled.
- Collection
- A Wix CMS collection with fields for language, alias, title, preview, rich content, SEO metadata, rubric, image, publish date, reading time and optional author data.
- Backend
- A POST function in
http-functions.jsthat validates a secret request header and processes every language underarticle. - Endpoint
- The published production
/_functions/...URL, entered in Blogent. - Response
- HTTP 200 with JSON
{"posted": true}, returned only after all languages are saved.
Frequently asked questions about the Wix integration
Is this a Wix app I can install?
No. It is backend code you add yourself in Velo. The page above lists exactly what the function must do, including the collection fields and the required response.
Why must the cover be imported into Media Manager?
The image field in the payload is a temporary URL. Importing it into Wix Media Manager gives the article a permanent image that will not expire.
What stops random requests from creating articles?
The function validates a secret request header before parsing the body. Requests without it are rejected.
How do I avoid duplicate articles?
Upsert by the stable combination of language and alias rather than inserting a new item on every request.
