Social integration overview
Self-host operator guides to connect posting channels — OAuth apps, API keys, extension session, and backend env.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Overview
Self-host operators
These guides are for people who run OpenQuok and register their own social developer apps. On OpenQuok Cloud, those apps are already configured — workspace owners only connect their accounts.
OpenQuok connects social channels through the backend integration layer. Each channel is organization-scoped. Workspaces can also call programmatic APIs with a opo_ token. See Public API authentication for token setup.
Connect models fall into three families:
- OAuth (most networks) — You create a developer app, set redirect URIs, request API access, and store client IDs and secrets in backend environment variables.
- Personal API key (for example Dev.to, Bluesky) — The user pastes a key in Add Channel; operators document which env vars apply per guide.
- Browser extension (Skool, Reddit) — No operator OAuth app. End users install from the Chrome Web Store on Chrome (or an unpacked build). Set VITE_OPENQUOK_BROWSER_EXTENSION_ID on the web build when you self-host. See Browser extension.
Danger
Never commit THREADS_APP_SECRET or other provider secrets. Use backend/.env.development.local locally or your host secret store in production.
Directory launch destinations (extension autofill, no posting OAuth) are documented under Directory integration and Directory submission.