Blogent

Make Integration

Custom webhook scenario that publishes every language before responding.

Make

Use a Custom webhook trigger and finish the scenario with an explicit Blogent success response.

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. Create a scenario with Webhooks → Custom webhook. Copy its URL. If you add a Make API key, enter x-make-apikey and its value in Blogent authorization fields.
  2. Run the scenario once and click Test connection in Blogent to capture the real article payload.
  3. Iterate over the languages inside article, publish or upsert one CMS item per language, and persist the temporary image before the scenario finishes.
  4. Place Webhooks → Webhook response last and return HTTP 200 JSON {"posted": true}. Enable immediate processing and test again.
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 Make, and Blogent will plan, write, link, and publish articles automatically.

Start now