SEO blog autopublishing via Make
Make receives the standard Blogent JSON payload through a Custom webhook. The scenario must publish every language inside article, move the temporary cover into permanent storage, and only then return the success response — Blogent treats that response as proof the article is live.
How to connect Blogent to Make
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.
- Create a scenario with Webhooks → Custom webhook. Copy its URL. If you add a Make API key, enter
x-make-apikeyand its value in Blogent authorization fields. - Run the scenario once and click Test connection in Blogent to capture the real article payload.
- Iterate over the languages inside
article, publish or upsert one CMS item per language, and persist the temporaryimagebefore the scenario finishes. - Place Webhooks → Webhook response last and return HTTP 200 JSON
{"posted": true}. Enable immediate processing and test again.
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 Make
- Works with any destination Make can reach, so a CMS without a native Blogent integration is still covered.
- An optional
x-make-apikeyheader can protect the webhook. - The scenario ends with an explicit Webhooks → Webhook response, so Blogent learns about a failed publish instead of assuming success.
- Immediate processing keeps the run synchronous with the connection test.
Requirements and compatibility
- Trigger
- Webhooks → Custom webhook; its URL goes into Blogent.
- Authorization
- Optional. If you use a Make API key, enter
x-make-apikeyand its value in the Blogent authorization fields. - Processing
- Iterate the languages inside
article, upsert one CMS item per language, and persist the temporaryimagebefore the scenario finishes. - Response
- Webhooks → Webhook response as the last module, returning HTTP 200 with JSON
{"posted": true}. - Verification
- The connection test sends a real article, not a ping.
Frequently asked questions about the Make integration
Why must the webhook response be last?
Blogent treats {"posted": true} as confirmation that publishing finished. Responding before the CMS modules run would report success for an article that does not exist yet.
How do I handle several languages?
Iterate over the article object and publish or upsert one CMS item per language, keeping each language’s own alias.
Do I have to store the cover image?
Yes. The image field is a temporary URL, so copy the file into permanent storage inside the scenario.
What does Test connection send?
A real, uniquely aliased article — not a ping. You verify it on the destination site before launch.
Put your SEO blog on autopilot
Create a blog, connect Make, and Blogent will plan, write, link, and publish articles automatically.
