Push PQ Intel buying signals into Salesforce as leads, contacts, or opportunities. Purpose-built for enterprise teams that need custom object mapping and account-level enrichment.
The PQ + Salesforce integration creates and updates Salesforce records based on PQ Intel buying signal detection. Using OAuth 2.0 via a Salesforce Connected App, PQ writes signal-enriched leads, contacts, and opportunities directly to your Salesforce org. Custom object mapping lets you map PQ fields to any standard or custom Salesforce field — including picklists, formula fields, and lookup relationships.
Signal data flows in near real-time: when PQ detects a new buying signal, a Salesforce record is created or updated within seconds. Historical signal data for existing accounts is backfilled on first connection, giving your team immediate visibility into past engagement. The integration supports bi-directional record lookups so your Salesforce workflows can reference PQ signal strength scores for routing and prioritization.
Lead/Contact name, email, company, title, phone, PQ ICP score, signal platform, signal excerpt, signal strength (hot/warm), signal timestamp, PQ profile URL, and any custom fields you define in the mapping interface.
In Salesforce Setup, navigate to App Manager > New Connected App. Enable OAuth Settings, set the callback URL to https://app.productquant.dev/auth/salesforce/callback, and select these OAuth scopes: Access your basic information (id, profile, email, address, phone), Access and manage your data (api), and Provide access to your data via Web browsers (web).
Copy the Consumer Key and Consumer Secret from your Connected App. In PQ Intel, go to Settings > Integrations > Salesforce and paste these credentials. Click Connect to initiate the OAuth flow.
Salesforce redirects you to its authorization page. Log in, review the requested permissions, and click Allow. PQ Intel will store the refresh and access tokens securely.
Choose which Salesforce object to create (Lead, Contact, or Opportunity). Map PQ fields to Salesforce fields using the on-screen builder. For example: PQ ICP Score → pq_icp_score__c, Signal Platform → pq_signal_platform__c, Signal Excerpt → Description. Click Save & Sync to activate.
In your Connected App's OAuth policies, set Permitted Users to Admin approved users are pre-authorized and assign the app to a permission set. Set Refresh Token Policy to Refresh token is valid until revoked so PQ can maintain continuous sync. Optionally configure IP Relaxation for your enterprise IP range. These settings ensure your OAuth connection remains stable across token refresh cycles.
In Salesforce Setup, navigate to Lead Assignment Rules and create a new rule for PQ-generated leads. Use filter criteria such as PQ ICP Score greater than 80 or Signal Strength equals Hot to route leads to the right queue or user. You can build multiple rule entries — for example, enterprise ICP leads go to the enterprise sales team, while mid-market leads route to the SDR team. Test your rules using the Evaluate Assignment Rules tool before enabling PQ sync.
Below is the default mapping from PQ Intel signal fields to Salesforce custom fields. Create these custom fields on the Lead (or Contact/Opportunity) object in Salesforce Setup before or during the mapping step.
| PQ Intel Field | Type | Salesforce Custom Field API Name | Field Type in Salesforce |
|---|---|---|---|
ICP Score |
Number (0-100) | pq_icp_score__c |
Number (3, 0) |
Signal Platform |
Text | pq_signal_platform__c |
Text (100) |
Signal Excerpt |
Text | pq_signal_excerpt__c |
Long Text Area (32768) |
Signal Timestamp |
Datetime | pq_signal_timestamp__c |
Date/Time |
Profile URL |
Text (URL) | pq_profile_url__c |
URL (255) |
Signal Type |
Picklist | pq_signal_type__c |
Picklist (values: buying_intent, tech_stack, job_change, funding, content) |
You can map PQ fields to any standard Salesforce field (e.g., Title, Department, Description) instead of custom fields. The mapping interface in PQ Intel supports one-to-one, many-to-one, and formula-based transformations. Changes take effect on the next sync cycle.
When PQ Intel detects a hot signal from a prospect matching your enterprise ICP, a Lead is created in Salesforce. As the prospect engages (follow-up signal detected), the Lead auto-converts to an Opportunity with the PQ score and signal timeline populated in custom fields. Your AE gets a fully qualified opportunity without manual triage.
For named accounts in your Salesforce Account object, PQ Intel enriches the account record with aggregated signal data — total signals detected, last signal date, hottest signal excerpt, and signal volume trend. Your account teams see engagement levels at a glance without leaving Salesforce.
Enterprise teams with custom Salesforce objects (e.g., "Engagement Log" or "Target Account") can map PQ signal data to any custom object. Define your own field mappings per object — PQ pushes signal data wherever your workflow needs it.
Salesforce access tokens expire after 2 hours by default. PQ Intel automatically refreshes the token using the stored refresh token, but if the refresh token itself has been revoked (e.g., user password change, admin revocation in Connected App OAuth policies), the integration will stop syncing. To fix this, go to Settings > Integrations > Salesforce in PQ Intel and click Reconnect OAuth to initiate a fresh OAuth flow. Ensure your Connected App's Refresh Token Policy is set to Refresh token is valid until revoked to prevent future expirations.
If syncs fail with an error like INVALID_FIELD or FIELD_INTEGRITY_EXCEPTION, the most common cause is a mismatch between the field API name in your mapping and the actual API name in Salesforce. Verify that each custom field exists in your Salesforce org using Setup > Object Manager > [Object] > Fields & Relationships. Field API names are case-sensitive — check for typos and ensure the __c suffix is present on custom fields. After correcting the mapping in PQ Intel, trigger a manual re-sync from the integration settings page.
Salesforce enforces API request limits per org (typically 5,000-25,000 calls per 24-hour rolling window depending on edition). If PQ syncs pause or fail with a REQUEST_LIMIT_EXCEEDED error, your org has hit its daily API limit. PQ Intel respects Salesforce's rate limits and will automatically throttle retries, but you may need to reduce the volume of signal data flowing through or upgrade your Salesforce edition for a higher limit. Monitor your API usage under Setup > Company Settings > Company Information > API Requests, Last 24 Hours.
If PQ confirms a sync completed successfully but the lead does not appear in Salesforce, check Object Permissions on the user profile or permission set that the Connected App uses. The user must have Read, Create, and Edit permissions on the Lead object (or whichever object you mapped). Also verify the user's role allows them to view all records — leads assigned to a queue or another user may not appear in your personal view. Use the All Leads list view to confirm the record exists, then adjust sharing rules or profile permissions as needed.
PQ Intel uses the industry-standard Salesforce Connected App pattern. You control the OAuth scopes granted, and you can revoke access at any time from Salesforce Setup > Connected Apps > Manage OAuth.
PQ requests only api and web scopes — it reads and writes only the objects and fields you configure in the mapping. It does not access users, profiles, permissions, or configuration data.
Access and refresh tokens are encrypted at rest (AES-256) and stored in PQ Intel's vault. Tokens are never logged, never exposed in browser storage, and are automatically rotated on each refresh cycle.
Enterprise customers can restrict PQ Intel API calls to a static IP range. Contact support to configure IP allowlisting for your Salesforce org.
Yes, PQ Intel supports multiple Salesforce connections. Each org requires its own Connected App and OAuth authorization. You can configure different field mappings and sync rules per org. Go to Settings > Integrations > Salesforce and click Add Connection to set up an additional org.
No. PQ Intel uses email address and company name as matching keys. If a Lead or Contact with the same email already exists in Salesforce, PQ updates the existing record with new signal data instead of creating a duplicate. You can also configure Salesforce duplicate rules and matching rules for additional deduplication.
PQ supports Salesforce Enterprise, Unlimited, and Developer editions. Professional edition is supported if your org has API access enabled. The integration uses the Salesforce REST API (v58.0+) and requires that your org has API access enabled in your user license.
New signals are pushed to Salesforce in near real-time — typically within 30-60 seconds of detection. Batch updates for existing account enrichment run every 15 minutes. Manual re-syncs can be triggered at any time from the integration settings page.
Yes. You can apply ICP-based filters in PQ Intel to sync only signals from prospects that match your target ICP score threshold. You can also filter by signal platform (e.g., only LinkedIn and GitHub signals), signal type, or minimum signal strength. These filters are configured in the integration settings alongside your field mappings.
If the Connected App or OAuth authorization is revoked, PQ Intel will lose access to your Salesforce org. The integration status will show as Disconnected in your settings. No data is deleted from Salesforce — existing records remain. To restore connectivity, create a new OAuth authorization by clicking Reconnect in the PQ Intel integration settings. You may need to re-enter your Consumer Key and Consumer Secret.
Get started with PQ Intel's Salesforce integration on the Scale+ plan. Connect your org, map your fields, and start receiving signal-enriched leads in minutes.
View plans & pricing →