All integrations
Webhook
By Bloggable
If it can receive a request, it can receive your writing.
Point the webhook at a URL and every publish, update and unpublish arrives there as JSON — the markdown and the rendered HTML both included, signed so your endpoint can prove it came from us.
How the Webhook integration works
What it does
- Both formats in one envelope.Markdown and HTML together, with the title, slug, excerpt, tags, cover image and the post’s Bloggable address alongside them. Optional values are sent as explicit nulls, so a field never disappears between posts and breaks a live scenario.
- Signed with HMAC-SHA256.The signature covers the timestamp and the raw body rather than the body alone, so a request captured today cannot be replayed next week.
- An idempotency key on every send.Retries carry the same key, so a receiver that dedupes on it will never publish the same post twice.
- Works with what you already automate in.Make, n8n, Pipedream, a Cloudflare Worker, or fifty lines in your own app. All it needs is an HTTPS endpoint that answers.
- Images stay as URLs.This is the one connection where images are not uploaded for you — your endpoint receives absolute image URLs and decides what to do with them. Said here rather than discovered later.
How to connect it
- 1Give it an endpointAny HTTPS URL that accepts a POST. Bloggable mints the signing secret rather than letting you choose one, because a secret you choose is a secret you reuse.
- 2Verify the pingA ping event goes out first. Check its signature against your secret before you trust anything else — verify the raw body, and compare in constant time.
- 3Arm itDecide whether posts send automatically. Every publish, edit and unpublish then fires its own event.
The platform