Overview - Self-host with Your Own Social Key

Connect social channels to OpenQuok — OAuth apps or a personal API key, backend env, and dashboard settings.

1 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Overview

Self-host only

These guides are for self-hosters who run OpenQuok themselves and register their own social developer apps. On OpenQuok Cloud, those apps are already configured — you only connect your account.

OpenQuok connects social channels through the backend integration layer: organization-scoped channels, optional programmatic APIs authenticated with a workspace opo_ token, and one of three connect families.

Most channels use OAuth. You apply for developer app , set redirect URIs, request API acess and store client IDs and secrets in backend environment. Some channels (for example Dev.to and Bluesky) use a personal API key the user pastes in Add Channel. Skool uses the browser extension — no operator OAuth app. Set VITE_OPENQUOK_BROWSER_EXTENSION_ID on the web app and distribute the extension; see Browser extension.

See Public API authentication for workspace API token setup.