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.
Set the webhook up from the Integrations page. It takes the single publishing slot like any other destination.
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.
Send on approval, or on schedule once you have moved the Copywriter up to publishing on its own.
Every agent starts switched off. You turn these on when you want them, one agent at a time.
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.
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.
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.
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.
Every agent starts with autopilot switched off, so nothing goes out until you press publish. When you are ready to hand more over there are four settings: off, write it and leave a draft, message you for a yes, or publish it on its own.
Settings apply per website - manage several sites from one account.