Webhooks
Notify Slack, Zapier, Make, or your own server every time AutoBlogger publishes an article. HMAC-signed payloads, retry on failure.
When webhooks fire
One webhook event: article.published. Fires after the post is successfully created in WordPress (status: published OR draft, depending on your publish mode). Failed generations don’t fire — webhooks only signal success.
Setup
Open AI AutoBlogger → SEO Settings → Webhooks:
- Toggle Webhooks enabled.
- Paste your endpoint URL (e.g.
https://hooks.slack.com/services/...or your own server). - Generate a signing secret (or paste your own). Used to compute the HMAC signature.
- Click Send test payload to verify your endpoint receives it.
Payload format
POST request, JSON body:
{
"event": "article.published",
"timestamp": "2026-04-25T14:32:18Z",
"site_url": "https://example.com",
"post": {
"id": 1234,
"title": "Why your sourdough starter keeps dying",
"url": "https://example.com/sourdough-starter-dying",
"excerpt": "Five common causes...",
"category": "Baking",
"style_profile": "Friendly how-to",
"word_count": 1842,
"featured_image": "https://example.com/wp-content/uploads/2026/04/...jpg",
"status": "publish"
},
"generation": {
"model": "gpt-5.4-mini",
"tokens_in": 1240,
"tokens_out": 2890,
"cost_estimate_usd": 0.0143
}
}HMAC signature verification
Every request includes header X-AutoBlogger-Signature: sha256=<hex>. Compute the same on your side using the request body + your signing secret:
// Node.js
const crypto = require('crypto');
const expected = 'sha256=' + crypto
.createHmac('sha256', SIGNING_SECRET)
.update(rawBody)
.digest('hex');
if (expected !== request.headers['x-autoblogger-signature']) {
return response.status(401).send('Invalid signature');
}Common integrations
Slack
Create an Incoming Webhook in Slack, paste the URL into AutoBlogger. The default payload is JSON; Slack only renders the text field, so use a Zap or Make scenario as a translator if you want a richer card.
Zapier
Create a Zap with the Webhooks by Zapier → Catch Hook trigger. Copy the URL into AutoBlogger. From there, fan out to social posting (Twitter, LinkedIn, Mastodon), email digests, Notion archives, anything Zapier can reach.
Make (Integromat)
Same flow as Zapier — use Custom Webhook trigger. Make’s lower per-task cost is a good fit for high-volume blogs.
Retry behavior
If your endpoint returns non-2xx, AutoBlogger retries with exponential backoff: 1 min, 5 min, 30 min, 2 hr. After 4 failures the event is dropped and logged in AutoBlogger → Logs. Endpoints should respond within 10 seconds; longer responses count as failures.
Next steps
Need a custom event?
More events (article.failed, queue.cleared, etc.) on the roadmap. Vote in support.