When your site runs on something without a native integration (a custom CMS, a static site pipeline, an internal tool), the Custom Webhook integration turns any HTTPS endpoint into a publishing destination. Every finished article is delivered as a JSON POST, ready for Zapier, Make.com, or code you wrote yourself.
A Real Integration, Not Just a URL
Webhooks are set up once under Account → Integrations and behave like any CMS integration: link one to a brand and finished articles publish through it automatically, whether they come from the writer, the agent, or the Content Calendar running on autopilot.
Built for Production Endpoints
Signed Deliveries
Add an optional signing secret and every delivery carries an HMAC SHA-256 signature in the X-Koala-Signature header, so your endpoint can verify each payload came from Koala AI before trusting it.
Stable Delivery IP
Deliveries always originate from a single stable IP address (published in our API docs), so locked-down servers can allow-list Koala AI instead of opening the endpoint to the world.
Simple Setup, Verified Before It Matters
- Add a Custom Webhook under Account → Integrations with your endpoint URL (a Zapier or Make.com webhook URL works as is) and an optional signing secret
- Click Send test to deliver a sample payload and inspect the exact request headers and your endpoint's response, before any real article depends on it
- Link the integration to a brand, and finished articles flow to your endpoint automatically
What Gets Sent
Every completed article is delivered as a single JSON POST to your endpoint:
POST <your endpoint>
Content-Type: application/json
X-Koala-Event: article.completed
X-Koala-Delivery-Id: <uuid> (same value on every retry)
X-Koala-Signature: sha256=<hex HMAC> (only when a signing secret is set)
{
"id": "1b2c3d4e-...",
"config": { "targetKeyword": "target keyword", "...": "the full article settings" },
"output": {
"html": "<h1>The Article Title</h1><p>Full article HTML...</p>",
"polishedHtml": "<h1>...</h1>... or null when polish did not run"
}
}This is the same body a per-folder Webhook URL sends, so a single endpoint handles both and you can switch between them freely.
Technical Details
- HTTP POST with a JSON payload: article id, the article settings, and both the raw and polished article HTML
- Event headers:
X-Koala-Eventidentifies the delivery type, andX-Koala-Signaturecarries the HMAC when a secret is set - Clear success semantics: any 2xx response counts as published; anything else is recorded against the article so you can see exactly what your endpoint returned
- Verification code included: the API docs include a copy-paste signature verification example
Note: a plain per-folder Webhook URL (set on the folder in your Library) and the bulk-writer webhookUrl parameter both still work, and send the same payload shown above. The Custom Webhook integration adds signing, automatic retries, a stable IP, test sends, and reuse across folders and brands.
Perfect For
Custom CMS Systems
Publish to proprietary content management systems
Automation Platforms
Chain Zapier and Make.com flows off every finished article
Hands-Off Publishing
Calendar autopilot articles land wherever you point them
Ready to publish anywhere? Try KoalaWriter and connect your endpoint in a couple of minutes.
Key Benefits
- Publish to Zapier, Make.com, or your own CMS
- HMAC-signed deliveries your endpoint can verify
- Stable delivery IP for server allow-lists
- Test sends that show the exact request and response
- Works with Content Calendar Autopilot and agent publishing
- Reusable integrations you can link per brand
Related Features
Ready to automate your content workflow?
Publish finished articles to any endpoint with signed, testable webhook deliveries.
Try KoalaWriter NowView Pricing Plans