SEO blog autopublishing via Make
Make connects the four Blogent actions to your existing CMS. Return each action’s complete result from the endpoint after the native CMS operation finishes.
How to connect Blogent to Make
Make
Use a protected synchronous endpoint that returns the complete result of every Blogent action.
Implement all four Blogent actions and return their final results. Zapier, Albato and ApiX-Drive require an authenticated callback; accepting a webhook does not confirm publication.
The test creates and updates one real article. Queue acceptance stays pending until each action returns its authenticated final result.
- Create Webhooks → Custom webhook with immediate processing. If configured, enter x-make-apikey and its secret in Blogent.
- Branch by
action: inventory lists existing native articles and next_cursor; read returns a full snapshot; create/update execute the CMS operation. - For writes, call a transactional CMS adapter with persistent operation_id receipts and atomic expected_revision checks. Preserve original target IDs, URLs, dates, authors and assets on update; never blindly upsert by alias.
- Return the complete action result only after all work finishes. In Make use Webhook response last; in n8n aggregate all locales before Respond to Webhook; in Wix return JSON from the awaited HTTP Function. Keep within Blogent’s request timeout.
- Run the connection test. Inventory, creation, authenticated read and update of the same article must all finish. A default webhook acknowledgment or a partial locale result cannot complete the test.
The four actions your endpoint must support
inventory— list existing articles. Acceptcursorandlimit; return{articles: [snapshot], next_cursor: string|null}. A null cursor marks the last page.read— read one article from the CMS. Accepttargetand/orcontent_id; return{article_snapshot: snapshot}. If nativetargetIDs are supplied, use those IDs.- A snapshot contains
identity, title, alias, date, article, target, revision, urls. Include the full content of every language, not just a summary. Use null for an unknown original date; URLs may be an empty map when unavailable. create— publish a new article in every supplied language. The request includes a uniqueoperation_id, a stablecontent_id, an emptytargetand nullexpected_revision. Return{posted:true,target,revision,urls}after saving.update— update the article identified bytarget. Checkexpected_revisionagainst its current version before writing. Keep its native IDs, URLs, aliases, original publication date, author and existing assets.
Blogent supports inventory, authenticated read, create and in-place update. Final receipts include native target IDs and revision; queued workflows complete through authenticated callbacks.
Test your connection
The test creates one article, reads it, updates it and reads it again. It compares every supplied language, full HTML, SEO fields, TOC and reading time. It leaves the test article on your website.
What you get after connecting Make
- Read the existing archive and full native snapshots before planning new articles.
- Update existing native articles while preserving IDs, URLs, original dates, authors and assets.
- Replay identical operations safely and reject stale revisions or changed operation reuse.
Requirements and compatibility
- Actions
- Implement inventory, read, create and update against the existing CMS and explicit locale mappings.
- Concurrency
- A transactional adapter with durable operation_id receipts and atomic expected_revision checks; individual no-code upserts are insufficient.
- Completion
- Return the final JSON result synchronously. Writes require posted:true, complete target IDs and revision.
Frequently asked questions about the Make integration
Does accepting the webhook confirm publication?
No. Blogent waits for the completed action result. A generic acknowledgment, an execution-history entry or a partial locale result does not finish the operation.
What does the connection test do?
Inventory, create, authenticated read and update of the same real article. It resumes while callbacks are pending and does not crawl the public page.
How are retries and edits protected?
The destination stores each operation ID, full request hash and receipt durably. Identical retries replay it; changed reuse and stale revisions return 409. Native editor changes must also advance the revision.
Similar integrations
Put your blog on autopilot
Connect your website and share what you know. Blogent takes it from there.