What it does
A webhook destination posts each published article to an https URL you choose, as JSON signed with the Standard Webhooks scheme. Use it for a platform Wavefront has no direct connection to, or for your own code.
Later versions arrive as update events, and a withdrawal arrives as a delete event, so your receiver can keep its copy in step.
Before you start
- An https URL on a public host that answers with a 2xx status
How to connect Webhook
- In Wavefront, open Settings → Publishing and choose Add destination. Pick Webhook.
- Enter a name and the receiver URL.
- Save, then copy the signing secret. Wavefront shows it once and keeps it encrypted.
- Choose Send test event to send a signed ping and see the status code your receiver answers.
- Check the signature in your receiver with the code samples in the webhook docs.
What Wavefront sends
- publication.create, publication.update and publication.delete events, plus a ping for tests
- The full article document: HTML and Markdown bodies, SEO title and description, canonical URL, categories, tags, author, JSON-LD and image URLs
- Retries with backoff on 429, 5xx and timeouts, always under the same message ID
- A delivery log of every attempt on the version page
- Secret rotation, with both secrets valid for 24 hours
Good to know
- Drafts and scheduling aren't offered: what happens after delivery is up to your receiver.
- Wavefront doesn't follow redirects. Set the final address.
- Zapier, Make and n8n don't check signatures, so for them the URL is the secret. Keep it private.