Skip to content

Social integration overview

Self-host operator guides to connect posting channels — OAuth apps, API keys, extension session, and backend env.

2 min read

Connect your agent today

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

Start your free trial

Overview

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.

Directory launch destinations (extension autofill, no posting OAuth) are documented under Directory integration and Directory submission.

Guides

Search documentation
Find a docs page
Discord Support