Blogent

Wix Integration

Velo HTTP Function that upserts articles into a Wix CMS collection.

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.

  1. 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.
  2. In Backend http-functions.js, implement a POST function, validate a secret request header, parse the JSON body, and process every language under article.
  3. 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.
  4. 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.
Official platform documentation
Universal webhook contract

This integration receives the standard Blogent JSON payload. Review the full contract — fields, HTML tags, response format — and try the live webhook tester.

Open webhook documentation

Webhook tester

Send a test article to your endpoint and check how the CMS processes the data. Edit the JSON if needed.

Edit the JSON to test different data and language codes.

Put your SEO blog on autopilot

Create a blog, connect Wix, and Blogent will plan, write, link, and publish articles automatically.

Start now