Publishing · Live

QuQi for Webhook

Send finished articles straight into a custom stack, from a headless Next.js blog to your own internal tools.

Connect Webhook Read the setup guide

Copywriter

Published to Webhook with its category, tags and cover, ready to rank.

Webhook · fernwaybikes.comPublished

Gravel bike size chart: find your fit in two minutes

Guidesgravelsizing

Connecting Webhook

If your site does not run on anything QuQi connects to directly, a webhook is the way in. Finished articles are sent to an endpoint you control, in a shape you can parse, and what happens next is your code's business. It is the same publishing slot as any other destination and behaves the same way, including holding the article and recording the reason when a delivery fails.

01
Give QuQi an endpoint
Set the webhook up from the Integrations page. It takes the single publishing slot like any other destination.
02
Handle the payload
Your endpoint receives the finished article and decides what to do with it. Anything the platform API can do, your own code can do too.
03
Choose the trigger
Send on approval, or on schedule once you have moved the Copywriter up to publishing on its own.

Who works with Webhook

CopywriterWrites the article that gets delivered.

What it handles for you

Finished articles delivered to any stack you can point at a URL
A publishing pipeline you control end to end
Failures recorded with the reason rather than dropped
The same approval settings as every other destination

Common questions about Webhook

When should I use a webhook instead of a direct integration?

When your site runs on something QuQi does not have a card for, or when you want to do something with the article before it becomes a page. A custom static site generator, an internal CMS or a review queue of your own are all good reasons. If you are on WordPress, Ghost, Webflow, Shopify, Wix or Notion, use the direct card instead, since it is less for you to maintain.

Is there an API as well?

Yes. The platform API is how a site outside QuQi reads the work QuQi has finished for it, and it is what the QuQi WordPress plugin and the QuQi Shopify app both use. If your site runs on something else you can call the same endpoints yourself rather than waiting for a webhook to arrive.

Does a webhook use my publishing slot?

Yes. A website publishes articles to exactly one destination, and a webhook is a destination like any other. Social channels and messaging are not affected and sit alongside it.

What happens if my endpoint is down?

The article is kept and the failure is recorded with the reason, so a bad deploy on your side never costs you the writing. You can send it again once the endpoint is back.