Set up knock-knock.

Prerequisites: a Discord server you can manage, and Developer Mode on (Settings → Advanced → Developer Mode) so you can copy IDs.

• Create the application and bot

  Go to discord.com/developers/applications → New Application → name it. Open the Bot tab → Reset Token → copy it. It's shown only once. This is your DISCORD_BOT_TOKEN.

• Enable the message-content intent

  Bot → Privileged Gateway Intents → enable MESSAGE CONTENT INTENT. The only privileged toggle you need. Without it the bot connects but reads empty message text.

• Invite the bot to your server

  OAuth2 → URL Generator → scope bot → enable these permissions, then let the server owner open the generated URL.

  View ChannelsSend MessagesSend Messages in ThreadsCreate Public ThreadsRead Message HistoryAdd ReactionsManage Messages

• Collect the id and your owner id

  Channel id — right-click the channel → Copy Channel ID (a 17–20 digit snowflake). Owner id — right-click yourself → Copy User ID (asked once per platform).

Then: run knock-knock setup, choose manage a bot -> add a new bot -> choose Discord; Add to a channel -> paste the channel id; then save/update token -> paste DISCORD_BOT_TOKEN.

Full fidelity over Socket Mode — an outbound WebSocket, no public server. Needs two tokens. (Inbound files work; outbound upload is pending.) Fast path: create the app from the manifest below — no clicking scopes one by one — then mint the two tokens.

• Create the app from this manifest skip the clicking

  On the page above: Create New App → From an app manifest → pick your workspace → paste the YAML below → Create. One paste sets every scope, event, interactivity, and Socket Mode — no adding them one chip at a time.

  display_information:
    name: knock-knock
  features:
    bot_user:
      display_name: knock-knock
      always_online: true
  oauth_config:
    scopes:
      bot:
        - app_mentions:read
        - channels:history
        - groups:history
        - im:history
        - mpim:history
        - chat:write
        - reactions:read
        - reactions:write
        - pins:write
        - files:read
        - files:write
  settings:
    event_subscriptions:
      bot_events:
        - app_mention
        - message.channels
        - message.groups
        - message.im
        - message.mpim
        - reaction_added
    interactivity:
      is_enabled: true
    socket_mode_enabled: true
    org_deploy_enabled: false
    token_rotation_enabled: false

  Rename it later by editing name / display_name — knock-knock fetches whatever the bot is called on connect, so the manifest name isn't binding.

• Generate the two tokens, then install

  The manifest can't mint tokens — do these two by hand:

  1 · App-Level Token — Basic Information → App-Level Tokens → Generate, add scope connections:write. This is SLACK_APP_TOKEN (xapp-…).

  2 · Bot token — OAuth & Permissions → Install to Workspace. This yields SLACK_BOT_TOKEN (xoxb-…). Then /invite the bot App to each channel.

• Collect the id and your owner id

  Channel id — channel name → View Channel Details → Copy Channel ID at the bottom (C0123ABCD). Owner id — your avatar → Profile → ⋯ → Copy member ID (U0123ABCD).

Then: run knock-knock setup, choose manage a bot -> add a new bot -> choose Slack; Add to a channel -> paste the channel id; then save/update token -> paste both tokens (SLACK_BOT_TOKEN + SLACK_APP_TOKEN, stored as the bot's app-token secret).

Live over getUpdates long-poll (no public server). One token, minor degrades (whitelist reactions, cold-DM).

• Create the bot via BotFather

  DM @BotFather → /newbot → copy the token (<id>:<secret>). This is your TELEGRAM_BOT_TOKEN. No extra secret.

• Disable Group Privacy & make it admin

  BotFather → /mybots → Bot Settings → Group Privacy → Turn off (else the bot sees only @mentions and looks "deaf"). Make the bot a group admin to receive reactions. Forum topics (the thread analogue) need a supergroup with Topics enabled.

• Collect the chat id and your owner id

  Chat id — via @userinfobot or getUpdates; groups are negative, supergroups -100…. Owner id — DM @userinfobot for your numeric user id.

Then: run knock-knock setup, choose manage a bot -> add a new bot -> choose Telegram, paste your user id; Add to a channel -> paste the chat id; then save/update token -> paste TELEGRAM_BOT_TOKEN. Gotcha: the bot can only DM users who have /started it — /start your own bot so approval DMs reach you.

Async transport (~60 s) over Notifications polling — best for PR-cadence coding and agent-to-agent-over-issues, not live chat. The repo is the room; an issue / PR is the task scope (automatic).

• Make a machine-user & a PAT

  Create a dedicated machine-user account to act as the bot, then a Personal Access Token at github.com/settings/tokens. Scopes: classic repo + notifications, or fine-grained Issues R/W + Pull requests R/W + Contents R/W + Metadata R. This is your GITHUB_BOT_TOKEN. No extra secret.

• Add the machine-user to the repo

  The machine-user must be a collaborator / org member of the repo so @mentions notify it and it can comment.

• The id and your owner id

  Channel id is the repo — owner/repo (each task scope owner/repo#issue is derived automatically). Owner id is your GitHub login.

Then: run knock-knock setup, choose manage a bot -> add a bot -> choose GitHub, paste login; Add to a channel -> paste owner/repo; then save/update token -> paste GITHUB_BOT_TOKEN. Gotchas: ~60 s latency; public repos are an injection surface — restrict to allowed authors; approvals arrive as a numbered text reply (host wiring is a known pending item).

Async over comment/page polling (~seconds, no reactions/buttons/DM/edit/inline files). Honest verdict: often better used as an MCP tool than a chat transport.

• Create the integration

  At notion.com/developers/connections create a connection with access token and capabilities of Read content, Insert content, Read comments, Insert comments, Read user information. It yields the secret NOTION_TOKEN (ntn_…). No extra secret.

• Share each page/database with it (might be automatically by Notion)

  Open the page or database → ••• → Connections → manage connections → add your integration. Without sharing, the integration sees nothing — the token alone grants no access. This is the single most common failure.

• The id and your owner id

  Channel id is a page or database id — 32 hex chars from the page link's trailing id. Owner id is your Notion user id (find it via settings -> profile -> user id).

Then: run knock-knock setup, choose manage a bot -> add a bot -> choose Notion; Add to a channel -> paste the page/database id and owner id; then save/update token -> paste NOTION_TOKEN. Gotcha: cold-start ignores the pre-existing comment backlog; the Workers/External-Agents bridge needs Business/Enterprise and is a future option.