Skip to main content

QQ Bot

The QQ Bot Channel receives events from the official WebSocket Gateway and sends replies through the platform API. The resident Gateway keeps the protocol session available.

What You Need​

  • a QQ Bot application;
  • the App ID;
  • the App Secret (entered in Anyy as client_secret);
  • optional Bot User ID; and
  • the Gateway intent for C2C and group @ messages.

See the current QQ Bot event subscription documentation.

Connect in Dashboard​

  1. Open Dashboard → Channel → Add.
  2. Choose QQ Bot, whose default entry uses WebSocket Gateway.
  3. Enter the App ID and App Secret.
  4. Add the Bot User ID only when you have the matching platform identity.
  5. Save the account credentials, then use the CLI wizard for policy changes.
  6. Enable the required C2C/group @ message intent in the QQ Bot console.

The default account ID is bot. No public inbound webhook is required for this profile.

Access Policies​

Direct messages default to pairing; groups default to mention. Supported policies are:

  • DM: pairing, open, allowlist, disabled;
  • group: mention, open, allowlist, disabled.
anyy channel pairing list
anyy channel pairing approve --request REQUEST_ID

Verify the Connection​

anyy channel doctor qqbot
anyy channel reload

Choose QQ Bot in the interactive anyy setup channel wizard to edit policy. Dashboard has no policy input or pairing-approval list, and current setup actions do not edit QQ allowlist entries. Replies require the original inbound message context; a historical conversation is not arbitrary proactive-send authority.

Test one C2C message and one group mention. Keep these as separate checks because they depend on different event paths and policies.

Diagnose intent problems before credentials

If identity probes succeed but no messages arrive, verify the Gateway intent and event subscription before rotating the App Secret.

Troubleshooting​

ProblemCheck
Gateway authentication failsApp ID and App Secret
Connected but no events arriveC2C/group @ message intent and app availability
Direct message ignoredDM policy and pairing/allowlist
Group message ignoredGroup policy and explicit bot mention
Receive works but send failsBot identity and platform send authorization