Get PQ Intel buying signals pushed directly into the channels your team already uses. No more tab-hopping or missed opportunities.
The PQ + Slack integration sends real-time buying signal alerts directly into your Slack workspace. Whenever PQ Intel detects a high-fit prospect exhibiting intent signals across LinkedIn, Reddit, Hacker News, Product Hunt, Telegram, or Medium, a structured notification lands in the Slack channel of your choice — complete with signal context, ICP match score, and a direct link to the full prospect profile. This means your sales and marketing teams stop reacting to leads hours or days late and start acting on buying signals within seconds of detection. Whether you run a single SDR desk or a distributed revenue team, Slack becomes your real-time revenue nerve center.
Each alert includes the prospect's name and company, which platform the signal was detected on, the signal excerpt, PQ's ICP match score, a warm/hot badge classification, and a deep-link back to the full PQ Intel profile for immediate action.
Navigate to https://api.slack.com/apps and create a new app, or use an existing one. Enable Incoming Webhooks and create a new webhook URL for your target channel.
Slack will provide a URL that looks like https://hooks.slack.com/services/T00/B00/xxxx. Copy this — it's the only credential you'll need.
In PQ Intel, go to Settings > Integrations > Slack. Paste your webhook URL and give the connection a name (e.g. "Sales Team"). Click Save & Test — PQ sends a test message to confirm the connection.
Select which ICP profiles and signal types trigger notifications. You can route hot signals to a #hot-leads channel, daily digests to #daily-report, or create per-ICP channels for each market segment.
Fine-tune what each alert includes. Choose between compact summaries (prospect name, company, signal type, score) or full-format notifications with signal excerpt, platform badge, ICP tags, and a deep link to the profile. You can also add custom labels or emoji prefixes to help your team scan channels at a glance.
Before going live, trigger a test signal from PQ Intel to confirm the webhook is working end-to-end. Check that the message arrives in the correct Slack channel with the right formatting, content, and deep links. If the test message includes a signal excerpt, click through to the profile URL to verify the full prospect data loads correctly.
A scheduled summary of every high-fit prospect that triggered signals in the past 24 hours. Includes aggregate counts per platform, trending ICP segments, and top-3 hottest leads with direct links. Perfect for your morning standup channel.
Instant notifications when PQ Intelligence rates a signal as "Hot" — meaning the prospect has a strong ICP match and high-intent buying behavior. These go straight to your #hot-leads channel so your SDRs can strike while the iron is hot.
Route signals to different Slack channels based on ICP segment. Enterprise-tier prospects go to #enterprise, SMB leads to #smb-pipeline, and partner opportunities to #partners. Each webhook gets its own filter rules.
PQ Intel only sends data to Slack — it never reads messages, channels, or user data. The webhook URL is the only permission needed, and it's write-only by design.
Because we use Incoming Webhooks, no OAuth tokens or bot tokens are exchanged. No message-scoping, no channel-reading, and no user access tokens ever leave PQ Intel.
All webhook payloads are sent over TLS 1.3. PQ Intel never stores Slack credentials — the webhook URL is encrypted at rest using AES-256.
Each webhook connection can be restricted to specific ICP profiles and signal types. Create multiple connections for different teams, each scoped to their relevant data only.
If alerts are not appearing in your Slack channel, first verify the webhook URL is correctly entered in PQ Intel — a single typo in the URL will prevent delivery. Next, check whether your network or VPN blocks outbound connections to hooks.slack.com. If your Slack workspace uses a custom allowlist, ensure hooks.slack.com is included. Finally, confirm the webhook has not been deleted from your Slack app settings page.
Each Slack webhook URL is bound to a specific channel at creation time. If messages arrive in the wrong channel, the webhook was likely created for a different channel than intended. Go to your Slack app's Incoming Webhooks settings, locate the webhook URL in use, and verify the Post to Channel field. Recreate the webhook with the correct channel if needed.
Receiving the same alert twice usually means multiple webhook connections in PQ Intel are configured to send to the same Slack channel. Check your PQ Intel integration settings — if you have more than one webhook pointing at the same channel, remove the duplicates. Also verify that no other team members have set up separate Slack integrations that route the same ICP and signal type combinations.
Slack webhook URLs do not expire on their own, but they can be revoked if the Slack app is deleted, the webhook is removed from the app settings, or workspace admin permissions change. If alerts stop working suddenly, go to https://api.slack.com/apps, open your app, navigate to Incoming Webhooks, and check whether the webhook still exists. If it was revoked, create a new webhook URL and update the connection in PQ Intel.
You need a Slack workspace where you have permission to create apps (typically a workspace owner or admin). From there, you create an Incoming Webhook at api.slack.com/apps and copy the webhook URL. No OAuth tokens, bot tokens, or API keys are required — just the URL. On the PQ Intel side, you need a Growth+ plan or higher.
Yes. Each webhook URL is tied to a specific channel at creation time, but you can create a new webhook for a different channel and update the connection in PQ Intel Settings > Integrations > Slack. Alternatively, create multiple webhooks (one per channel) and route different ICP profiles or signal types to each. This lets you keep #hot-leads, #daily-digests, and #enterprise as separate destinations.
Yes. When configuring each webhook connection in PQ Intel, you can choose between compact and full notification formats. Compact mode shows key fields only (name, company, signal type, score), while full mode includes the signal excerpt, ICP match tags, platform badge, and a deep link. You can also set custom labels and emoji prefixes to help your team visually distinguish alert types at a glance.
Absolutely. You can create as many webhook connections as you need, each pointing to a different Slack channel. This is useful for routing different ICP segments (enterprise, SMB, partners) to their respective team channels, or sending real-time hot signals to one channel while daily digests go to another. Each connection can have its own filter rules for ICP profiles and signal types.
Slack's Incoming Webhooks are subject to the same rate limits as the broader Slack API: approximately 1 message per second per webhook URL. For typical PQ Intel usage — where alerts arrive sporadically as signals are detected — this is more than sufficient. If you have a very high-volume setup, consider distributing alerts across multiple webhooks and channels to stay well within limits.
To stop receiving alerts, simply delete the webhook connection from PQ Intel by going to Settings > Integrations > Slack and clicking Remove next to the connection. You can also delete the webhook URL from your Slack app settings at api.slack.com/apps to revoke it entirely. No data is retained after disconnection — you can reconnect later by creating a new webhook.
Connect PQ Intel to your workspace in under 60 seconds and turn real-time buying signals into revenue.
See plans & pricing →