Directory integration overview
How directory launch destinations differ from OAuth social channels in OpenQuok.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Two channel families
OpenQuok talks about channels in two ways:
| Family | Connect model | What OpenQuok automates |
|---|---|---|
| Social | OAuth, API key, or extension session for posting | Schedule and publish posts from the composer, calendar, and agents |
| Directory | No OAuth to the directory | Autofill submit forms from your business profile; you submit on the directory site |
Social channels appear on My Dashboard with avatars and post to networks on a schedule. Directory destinations appear on My Products and in the public directory launch platforms section of the Channels hub.
Note
The public API and CLI still use integration for connected social accounts. Directory launches use the dashboard auto-launch API. They are not the same as posting with POST /public/posts.
How a directory destination is built
Behind each launch path OpenQuok stores:
- A start URL on the directory site (submit form, pricing page, and so on)
- Extension config that maps profile fields to form inputs
- Optional links to Build Backlinks editorial rows for cost and dofollow context
Operators can add catalog rows through internal tools. Shipped exemplars also live in database seeds. New social networks use Adding a provider. New directory sites follow the auto-launch contribution path in engineering documentation.