Turn every PQ Intel buying signal into a trigger for any app in your stack. Send leads to your CRM, post alerts to Slack, log rows to Sheets, or kick off multi-step Zaps — all without writing a single line of code.
The PQ + Zapier integration connects PQ Intel's buying signal engine to over 7,000 apps through Zapier's trigger-and-action framework. When PQ Intel detects a new prospect signal that meets your ICP criteria, it fires a webhook payload containing the full signal context — prospect name, company, platform source, signal excerpt, ICP match score, and signal classification (Warm/Hot). Zapier passes that payload to any connected app as the trigger for subsequent actions.
This integration is designed for revenue teams that want to eliminate manual lead handling. Instead of logging into PQ Intel to check for new signals, your CRM gets updated automatically, your Slack channels get pinged in real time, and your analytics sheets stay current — all driven by the same buying signal data you already rely on for pipeline generation.
The webhook-based architecture means you can chain multiple actions in a single Zap: create a HubSpot contact, then post a Slack alert to your sales channel, then log the interaction to Google Sheets — all from one signal detection. Because the payload is structured JSON, you can use Zapier's built-in Formatter step to transform, split, or combine fields before passing them downstream.
Auto-create contacts in any CRM (HubSpot, Salesforce, Pipedrive, Close, Copper), post formatted alerts to Slack or Teams, log leads to Google Sheets or Airtable, create tasks in Asana or Monday.com, send email alerts via Gmail or Outlook, and chain multiple actions in a single Zap for complex automation workflows. You can also use Zapier's Filter step to route only signals above a certain ICP score to specific actions, creating conditional workflows without any code.
In Zapier, create a new Zap and select Webhooks by Zapier as the trigger app. Choose Catch Hook as the trigger event. Zapier generates a unique webhook URL — copy this URL.
In PQ Intel, go to Settings > Integrations > Zapier. Paste your Zapier webhook URL and add a name for the connection (e.g. "CRM Sync"). Click Save & Test — PQ sends a sample payload to verify the webhook is reachable.
Back in Zapier, Zapier's test feature will detect the sample payload from PQ Intel. Use the test data to map fields — map prospect_name to the contact name field, signal_excerpt to the description, icp_score to a custom score field. Test the action step to confirm the mapping works.
Add an action step in Zapier and select your target app — HubSpot, Salesforce, Slack, Google Sheets, or any of the 7,000+ supported apps. Choose the action event (e.g. "Create Contact" in HubSpot, "Send Channel Message" in Slack, "Add Row" in Sheets). Map each PQ Intel field from step 3 to the corresponding field in your target app. Use the field mapping table below as a reference for available PQ Intel output fields.
After mapping fields, run Zapier's test to send a real sample through to your target app. Verify the data landed correctly — check that the contact name, company, signal excerpt, and ICP score all appear in the right fields. If something looks off, adjust the field mapping and re-test. For Slack alerts, confirm the message formatting displays correctly. For Sheets, verify the columns align with your headers.
Once the end-to-end test passes, name your Zap and toggle it to On. Every new PQ Intel signal meeting your filter criteria will now automatically trigger your Zap. You can monitor Zap runs from the Zapier dashboard — each successful run shows the input payload and output result. Turn off the Zap at any time if you need to adjust mappings or filters.
When PQ Intel sends a signal to Zapier, the webhook payload includes the following fields. Use these field names in the Zap editor to map data to your target app. All fields are included in every payload — empty fields are omitted to keep payloads compact.
| Field Name | Description | Type | Example Value |
|---|---|---|---|
| prospect_name | Full name of the detected prospect | string | Sarah Chen |
| prospect_company | Company name associated with the prospect | string | Acme Corp |
| prospect_title | Job title of the prospect (if available) | string | VP of Engineering |
| prospect_linkedin | LinkedIn profile URL of the prospect | url | https://linkedin.com/in/sarahchen |
| signal_excerpt | Full text content of the detected signal | text | Looking for a solution to automate our sales outreach... |
| signal_source | Platform where the signal was detected | string | linkedin, reddit, hackernews |
| signal_url | Direct URL to the original signal post or comment | url | https://reddit.com/r/sales/... |
| signal_type | Classification of the signal type | string | question, pain_point, vendor_search |
| icp_score | ICP match score from 0-100 | integer | 87 |
| signal_classification | Overall signal priority rating | string | Hot, Warm |
| timestamp | ISO 8601 timestamp when the signal was detected | datetime | 2026-05-18T14:30:00Z |
If your Zap isn't working as expected, check these common scenarios before reaching out to support.
prospect_name not name, icp_score not score). Re-run the Zap test with a fresh sample payload to see which fields contain data. Use Zapier's Formatter step to transform data types if needed — for example, convert the integer icp_score to a string for apps that don't accept numeric fields.prospect_name, prospect_company, signal_excerpt, signal_source, icp_score (0-100 integer), signal_classification (Warm/Hot), signal_url, prospect_title, prospect_linkedin, timestamp, and signal_type. All fields appear in the Zapier field mapper once you send a test payload.Whenever PQ Intel detects a qualified lead, automatically create a new contact or lead record in your CRM — HubSpot, Salesforce, Pipedrive, Close, or Copper. The contact is pre-populated with signal context, ICP match score, and a deep-link back to the full PQ Intel prospect profile.
Route "Hot" rated signals to a dedicated Slack channel with a formatted message containing the ICP score badge, signal excerpt, platform source, and a direct link to act on the lead. Your SDRs get pinged the moment a high-intent prospect surfaces.
Maintain a running log of all detected signals in Google Sheets for manual review, team collaboration, or downstream analysis. Each row includes timestamp, prospect name, company, signal source, ICP score, and status. Use filters and pivot tables to spot trends across your pipeline.
PQ Intel pushes data to Zapier via a webhook URL — it never reads from Zapier or accesses your connected apps directly. The webhook URL is the only credential exchanged, and it's write-only by design.
Each webhook request includes a PQ Intel API key in the header for payload verification. You can rotate the key at any time from your PQ Intel settings. Invalid or expired keys are silently rejected.
All webhook payloads are sent over TLS 1.3. PQ Intel never stores Zapier credentials beyond the encrypted webhook URL (AES-256 at rest). Payloads contain only signal metadata — no raw conversation data or personal contact details unless explicitly configured.
Each Zapier connection can be scoped to specific ICP profiles, minimum signal scores, and signal platforms. Create multiple connections for different workflows — CRM sync only gets high-scored leads, while the analytics sheet gets all signals.
Connect PQ Intel to Zapier and start routing buying signals to your CRM, Slack, Sheets, and more — all without code. Upgrade to Growth today.
See plans & pricing