QuQi DOCS Open console
ESC
Open console Platform API
GETTING STARTED
What QuQi is Add your website Business and brand The dashboard
AUTOMATION
Autopilot Approvals Schedules & cadence Notifications
AGENTS
Meet the agents How skills work SEO Auditor Content Planner Copywriter Social Planner Social Copywriter Image Designer Video Producer Link Exchange Website Analyzer Brand Kit Growth Strategist Publisher
WORKSPACES
Content calendar Studio Image library
INTEGRATIONS
Integrations Connect WordPress Connect Shopify Connect social channels Telegram & WhatsApp Connect Ghost Connect Webflow Connect Wix Connect Notion Your own endpoint Google Search Console
PLANS & USAGE
Plans Usage and limits Buying more
TROUBLESHOOTING
Nothing was published The approval message never arrived An agent did not run You hit a limit
Docs / Integrations / Integrations

Integrations

What a connection actually gives you, everything QuQi can connect to, and the rules that apply to all of them.

5 min read All plans

QuQi writes articles, posts and pictures on its own. A connection is what lets it put them somewhere — your website, your social accounts, your phone. Until you connect something, everything QuQi makes stays inside QuQi.

START HERE Connections belong to one website, not to your account. Set them up under Integrations for each website in turn — one account can run a WordPress blog and a Shopify store side by side, each with its own credentials. Only an owner or admin of a website can connect or disconnect anything for it.

The four groups

The Integrations page sorts everything into four sections.

GROUPWHAT IT CONNECTSWORTH KNOWING
Publishing Where finished articles go — WordPress, WordPress.com, Ghost, Webflow, Shopify Blog, Wix Blog, Notion, or a webhook of your own. Only one at a time.
Website analytics Google Search Console, for the clicks, impressions and queries your site already gets. You sign in with Google.
Social channels Instagram, Facebook, TikTok, YouTube, LinkedIn, X, Threads, Pinterest and Google Business. One click each.
Talk to QuQi Telegram and WhatsApp, for approval messages and for asking QuQi things from your phone. No credentials needed.
One home for your articles. All nine for your posts.

Articles publish to exactly one place

You pick one publishing destination per website. Once one is connected, the other publishing cards show a quiet “in use” note instead of a Set up button, and connecting a second is refused until you disconnect the first. A destination connected through the QuQi WordPress plugin or the QuQi Shopify app holds that one slot too.

Nothing else is limited this way. Social channels and messaging sit alongside your publishing destination, and you can have all nine social channels connected at once.

A saved connection is a working one

QuQi proves the credentials before it stores them, so a connection you can see on the page is one that worked. If a connection attempt is refused, you get the destination’s own explanation — for example that WordPress rejected those credentials — rather than a generic error.

CAREFUL Credentials can stop working later. When a stored publishing credential is refused, QuQi names the one that failed and asks you to reconnect that one.

What each kind of connection unlocks

  • A publishing destination lets a finished article be pushed to your live site. Publishing needs a plan that includes CMS publishing — generating the article does not.
  • A social channel lets a written post actually go out. Publishing to social needs an active paid plan; the trial covers generation only.
  • Google Search Console brings the clicks, impressions and query data for your site into QuQi. QuQi asks only for read-only access and never edits your property.
  • Telegram or WhatsApp carries approval messages and lets you talk to your agent from your phone.

You can plan before you connect

Nothing is blocked by an empty Integrations page. The Social Planner still fills the week with nothing connected, and you can plan and write a post for a channel before that channel exists — the calendar marks the channel as unable to publish, and the publisher refuses at send time rather than dropping the post silently.

The reverse is also true: connecting a channel does not make anything go out. Every agent starts with autopilot switched off.

Did this page answer your question? Yes Not quite