Skip to main content
Push An hour or two of developer time

Publish to Webhook

The escape hatch that makes "any CMS" true. Give Vupie a URL and every finished article is POSTed to it as JSON: the full HTML, the metadata, the images and the citation list. What your stack does next is entirely your call.

Setup

How you connect it.

What you need

An HTTPS endpoint that accepts POST, and somewhere to keep the shared secret.

  1. 1

    Add your endpoint URL in the site's Integrations panel in Vupie and copy the signing secret.

  2. 2

    Verify the HMAC signature on your side using that secret, and reject anything that does not match.

  3. 3

    Map the payload into your own content model.

  4. 4

    Fire a test delivery from the panel until your handler is happy.

On publish

What Vupie fills in for you.

Not just the body text. The fields that decide whether the page is indexable and linked are set on the way in, because an article nobody can find is not published, it is stored.

Full article HTML
Title, slug, excerpt and meta description
Image URLs and alt text
Tags and category hints
The citation list
The quality score and the scheduled publish time

Before you pick this route

Worth knowing about Webhook.

Signed, so you can trust it

Each delivery carries an HMAC signature computed with your shared secret. Verify it before you act on the payload.

You own what happens next

Publish immediately, queue for review, translate, route by category. Vupie stops at the POST.

Tell us the live URL

Index inspection and AI-visibility tracking need to know where the article ended up, so report the final URL back or expose it in your sitemap.

The same on every destination

The integration decides where. It does not decide what.

Whichever route you pick, the article behind it went through the same pipeline. Choosing Webhook changes the plumbing, nothing else.

The full method

Researched before written

Primary sources retrieved and tiered, your own numbers computed from your data, and the two or three questions only you can answer sent by SMS or Slack. The model may cite only from that list.

Reviewed by another vendor

Every draft is checked by a model from a different vendor than the one that wrote it. Sections below threshold are rewritten up to twice, and what still fails is refused rather than published.

Images, links and schema

Images with provenance metadata, internal links into your existing pages, and Article schema, all set through the integration rather than left for you to add.

Index inspection after publish

The URL is checked on days 2, 7 and 14 to confirm it was actually indexed, and AI-visibility tracking watches whether ChatGPT, Perplexity and Gemini start citing it.

Connect it once. Then it publishes without you.

Setup is an hour or two of developer time, and it is the last time you have to touch it. After that, articles land on the calendar you approved.