High-intent leads are only useful if they land where your team actually works. VocLens can route every synced lead to Slack, Notion, and Discord — here's exactly how to wire each one up.

Prerequisite: connect at least one YouTube channel first (Dashboard → Connect YouTube). Integrations only fire on synced comments.

Where to configure

Open Integrations from the app sidebar. You'll see three cards — Slack, Discord, Notion — plus an optional custom webhook. Each card has a Save & connect button, a Test button (after connecting), and a disconnect control.

1. Slack (OAuth — no webhook needed)

Slack uses the modern OAuth app flow, so you don't copy any URL — just authorize once.

  1. On the Slack card, click Connect with Slack.
  2. Approve the VocLens app in the Slack popup (this grants the chat.postMessage, channels:join, and channels:history scopes).
  3. You're redirected back; the card now shows Connected to <your workspace> and a channel picker.
  4. Pick the channel where lead alerts should post, then it's live.

What you get: every high-intent lead arrives as a Block Kit card with the commenter's avatar, channel, subscriber count, and a deep link to the exact video moment. Hit ✓ Mark contacted right inside Slack and the status writes back to VocLens — no tab-switching.

Notes:

  • The bot must be in the chosen channel. For public channels it auto-joins; for private channels, run /invite @voclens in that channel first.
  • Legacy webhook-only configs still work as a fallback (no interactive button) — paste an Incoming webhook URL (https://hooks.slack.com/...) instead of using OAuth.

2. Discord (incoming webhook)

Discord needs a single webhook URL per target channel.

  1. In your Discord server, go to Server Settings → Integrations → Webhooks → New Webhook.
  2. Name it (e.g. "VocLens Leads"), choose the channel to post to, and click Copy Webhook URL.
  3. On the Discord card in VocLens, paste it into Webhook URL (https://discord.com/api/webhooks/...).
  4. Click Save & connect, then Test.

Each lead posts as a rich embed: author (with avatar + profile link), the comment text, subscriber count, and a link to the exact YouTube moment. If you later enable digest/auto-push rules, Discord emits one combined summary message instead of one per lead.

3. Notion (integration token + shared database)

Notion needs an integration token and a database the integration can write to.

  1. Go to https://www.notion.so/my-integrations and click New integration. Name it (e.g. "VocLens"), pick the workspace, and submit.
  2. Copy the Internal Integration Secret (secret_xxx). Paste it into Integration token on the Notion card.
  3. Open the Notion database you want leads to land in. Click ••• → Connections → Connect to, and select your new "VocLens" integration. (The integration must have access, or writes fail.)
  4. Copy the Database ID from the database's URL — it's the 32-character hex string between https://www.notion.so/<workspace>/ and the ?v= query: https://www.notion.so/myws/a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6?v=... Paste it into Database ID.

Default property mapping (auto-created if missing):

Notion property VocLens field Type
Name Comment text (truncated to 200 chars) Title
Author @handle Text
Intent High / Support / General Select
Channel Channel name Text
Video Url YouTube permalink URL
Subscribers Author subscriber count Number
Profile Author profile URL URL
Avatar Author avatar File
Published Comment publish time Date
Status New Select

Optional property mapping: if your database uses different names, expand Show property mapping (optional) and set Title property, Author property, Intent property, and Channel property to match your schema. Any mapping you leave blank falls back to the defaults above.

  1. Click Save & connect, then Test (the test calls Notion's users/me endpoint to validate the token).

Testing and troubleshooting

After connecting, always hit Test:

  • Slack (OAuth): posts "🔧 VocLens connection test — you're all set!" to your chosen channel.
  • Discord: posts the same test message to the webhook channel.
  • Notion: validates the token; a 401/invalid means the secret is wrong, a 403 usually means the database wasn't shared with the integration.

Common fixes:

  • Slack private channel silent-fails → /invite @voclens in that channel.
  • Notion "Could not find database" → the integration isn't connected to that database (step 3 above).
  • Discord "invalid webhook" → the URL must contain discord.com/api/webhooks.

Route by intent

Once all three are connected, control what goes where with Auto-Push Rules (sidebar → Noise rules). For example, send High-intent leads to Notion as CRM records and keep General chatter as ambient Slack/Discord alerts — so the work becomes closing leads, not hunting for them.