SEO blog autopublishing via Zapier
Zapier connects the four Blogent actions to your existing CMS. The workflow returns each final result through the supplied authenticated callback; its initial webhook acknowledgment leaves Blogent waiting.
How to connect Blogent to Zapier
Zapier
Use an incoming webhook workflow with a final authenticated callback for 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 by Zapier → Catch Hook (or Catch Raw Hook to retain headers). Use the hook URL in Blogent and select Zapier.
- 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.
- Add Webhooks by Zapier → Custom Request as the final callback step. Keep request_id, callback_url and callback_token through the workflow. Add a final HTTP POST action to callback_url using Authorization: Bearer callback_token and JSON {contract_version:"2.0",request_id,action,result}. Send an explicit failed result on error.
- 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.
If you connect through Zapier, Albato or ApiX-Drive
- This section applies to those three platform connections. A custom webhook returns its result directly. For queued workflows, select the platform in your project’s integration settings.
- Every action includes
request_id,callback_urlandcallback_token. Keep them through all workflow steps. Run the requested action against your CMS with the same storage, retry and revision protections described above. - After the action finishes, POST to the supplied callback URL with
Authorization: Bearer <callback_token>. Send{contract_version:"2.0",request_id,action,result}, where result is the action’s complete response. - On failure, send
result:{posted:false,message:"reason",status:409}with the appropriate 4xx/5xx status value. Never report success for a partially saved article. - The callback is valid for one hour and is tied to its request, action and configuration. Identical repeats are accepted; changed results return 409, invalid tokens 401 and expired requests 410. The system may resend the same request up to five times, at least two minutes apart. Deduplicate by request_id and operation_id.
- The connection test waits for callbacks at each step: inventory → create → read → update → read. The final read checks the stored changes. Also test invalid tokens, duplicate callbacks and expired requests.
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 Zapier
- 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
- POST the final result to callback_url using Authorization: Bearer callback_token. Preserve request_id and action.
Frequently asked questions about the Zapier 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.