WordPress is where most QuQi articles end up, and connecting it is what turns a finished draft into a live page without you opening the admin. The article arrives with its category, its tags and its featured image already set, and the images are uploaded into your own media library rather than linked from somewhere else. There are two ways in: connect the site from the Integrations page, or install the QuQi AI plugin and connect from the WordPress side.
Set it up from the Integrations page, or search for the QuQi AI plugin under Plugins then Add New in your own admin. The plugin needs WordPress 5.8 or newer and PHP 7.4 or newer, and signs in with a website API key you create under Settings then API Keys.
Pick the category and tags new articles should carry, and whether they arrive as drafts for you to read or go straight to the site.
Leave approval on and every article waits on your calendar. On autopilot, an article only reaches your live site when the mode is set to publish it.
Every agent starts switched off. You turn these on when you want them, one agent at a time.
No. You can connect the site straight from the Integrations page and never touch WordPress itself. The QuQi AI plugin is the other way round, for people who would rather connect from inside their own admin, and it is on the WordPress plugin directory. Either route takes the same publishing slot, so pick whichever you find easier and ignore the other.
Two different ones, on purpose. The Copywriter writes the article from a topic the Content Planner booked, and stops there. The Publisher is what actually pushes it to WordPress, sets the category and tags, uploads the images and reports back. Keeping them apart is why a publishing failure never costs you the writing.
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. Set the Copywriter to publish it and articles go to your site on schedule with nothing for you to do. Most people run on drafts for a few weeks first, read what turns up, then hand over publishing once the voice is right.
The article is kept and the failure is recorded, so the writing is never lost. You are told what WordPress itself said rather than a generic error, which usually points straight at the cause, and you can publish it again once it is sorted. The same is true at connection time: if credentials are rejected you get the reason.
One publishing destination per website, but an account can hold as many websites as you like, each with its own connection and its own settings. So a WordPress blog and a Shopify store can run side by side under one login. What you cannot do is point one website at two destinations at once.
Settings apply per website - manage several sites from one account.