C8 - Integrations

Connecting PersistIQ with your CRM and other tools, plus the Chrome extension.

By Andres Miramontes

• 7 articles

8.1 PersistIQ Chrome Extension

What it does 12 integrations The PersistIQ Chrome Extension works where you're already researching: websites, LinkedIn, and social profiles. Three core abilities: 1. Find emails — locate verified email addresses for people you're viewing on the web. 2. One-click add — push the person into PersistIQ as a prospect, or directly into a campaign, without opening the app. 3. Push from CRM — send leads from your CRM into PersistIQ to start outreach. Installing 1. Open the Chrome Web Store and search for the PersistIQ extension. 2. Click Add to Chrome. 3. Sign in with your PersistIQ account. Typical workflow 1. You're researching a prospect and find a good fit. 2. The extension surfaces their email on the page. 3. One click adds them to PersistIQ — with fields filled where available. 4. Choose the campaign (or add as a standalone prospect). 5. Back in the app, fill snippets and attach them to the campaign. Notes - The extension requires Chrome or a Chromium-based browser. - It's a prospecting surface — the full app at persistiq.com/app remains where campaign work happens.

Last updated on Nov 13, 2026

8.2 Salesforce integration

What the sync does 12 integrations The PersistIQ Salesforce integration is bi-directional. It connects your CRM records with your outreach so neither system goes stale: - Create leads/contacts — prospects added in PersistIQ can be created in Salesforce. - Update status and fields — changes flow between systems (e.g. outreach status written back to the lead record). - Log activities — emails sent, opens, and replies are recorded on the Salesforce record. Why it matters for outbound - Reps stop living in two databases — the CRM shows what outreach is doing. - Opt-outs and replies are visible to anyone touching the account, not just the SDR. - Reporting can be joined against CRM data (pipeline created, not just emails sent). Setup overview 1. Get help from your Salesforce admin — the integration needs API permissions. 2. Connect from the Integrations page in PersistIQ settings. 3. Authorize with your Salesforce org. 4. Map PersistIQ fields to Salesforce fields. 5. Choose sync behavior (which records create which, in which direction). 6. Test with one lead end-to-end before turning it on broadly. [CONFIRM: exact sync options and field-mapping capabilities in the current integration]

Last updated on Nov 13, 2026

8.3 Copper integration

What it does 12 integrations The Copper integration connects your Copper CRM contacts to PersistIQ outreach, so contacts in Copper can be added to campaigns. Typical workflow 1. Connect Copper from the Integrations page in PersistIQ settings. 2. Authorize your Copper account. 3. Select Copper contacts and add them to a PersistIQ campaign. 4. Outreach activity flows back to your Copper records. Good to know - Before adding Copper contacts to campaigns, confirm your opt-out list — CRM contacts may include people who've already unsubscribed. - Use the CRM email to bcc setting on your mailbox as a lightweight activity log if you don't want full sync. [CONFIRM: exact sync direction and activity logging options for Copper]

Last updated on Nov 13, 2026

8.4 Pipedrive integration

What it does 12 integrations The Pipedrive integration links contacts in your Pipedrive CRM with PersistIQ campaigns, so you can push CRM contacts into outreach and keep activity visible. Setup 1. Open the Integrations page in PersistIQ settings. 2. Connect and authorize your Pipedrive account. 3. Choose how contacts flow to PersistIQ. 4. Add them to campaigns and start outreach. Good to know - CRM lists are mixed-intent by nature: exclude customers, opt-outs, and old loses before adding contacts to cold campaigns. Build that filter in Pipedrive first. - Combined with the mailbox's CRM email to bcc setting, sends get logged on the Pipedrive record even before deep sync is configured. [CONFIRM: current sync capabilities and field mapping for Pipedrive]

Last updated on Nov 13, 2026

8.5 Webhooks

What webhooks are 12 integrations Webhooks push events to you as they happen: instead of polling the API, PersistIQ sends an HTTP POST to your endpoint when something occurs — a prospect replied, an email bounced, a prospect opted out. What they're good for - Real-time reply alerts — post to Slack so replies get worked within minutes. - Sync to a data warehouse — build your own outreach analytics on top of raw events. - CRM enrichment — write outreach state back to any system, not just the native integrations. - Internal workflow automation — route bounced VIP prospects to an ops queue. Getting started 1. Stand up an HTTPS endpoint that accepts POST requests. 2. Register the URL on the Integrations page (see also the API & Webhooks collection for event types). 3. Test with a low-stakes event before pointing production systems at it. Reliability basics - Respond quickly (2xx) and process asynchronously — long processing causes timeouts. - Be idempotent: retries mean you may receive the same event twice. [CONFIRM: exact webhook event list and payload format from the API documentation]

Last updated on Nov 13, 2026

8.6 Personas and Segment

Personas 12 integrations Personas is a lead-gen provider integration: it automatically adds leads to your PersistIQ account daily. Instead of sourcing lists manually, Personas delivers matching prospects on an ongoing schedule. - Define the persona — the profile of the prospect you want. - Leads matching that profile are added automatically each day. - Review them like any other prospects before adding to campaigns: snippets don't write themselves. Segment Segment (Twilio Segment) integration syncs opt-outs: unsubscribe events from your other tools flow into PersistIQ so that a prospect who opted out anywhere is respected here. - Connect Segment from the Integrations page. - Opt-out events sync across systems. - Result: one consistent opt-out truth instead of per-tool lists. Where to connect both Both are available on the Integrations page in PersistIQ settings. See Getting your API key in the API & Webhooks collection for the developer context that often accompanies these setups. [CONFIRM: current availability and configuration options for Personas and Segment]

Last updated on Nov 13, 2026

8.7 Zapier integrations

Why Zapier 12 integrations Zapier connects PersistIQ to tools that don't have native integrations, with no code. If your workflow lives in HubSpot, Calendly, or Google Sheets, Zapier bridges it. Popular connections - HubSpot - Calendly — meeting booked → update the prospect in PersistIQ (booked prospects should exit or pause sequences automatically). - Typeform — form response → create prospect in PersistIQ. - Zoho CRM - Google Sheets — sheet rows → prospects, for teams that manage lists in spreadsheets. - Airtable - Nimble, Podio, Microsoft Dynamics 365, Sugar, Bullhorn, Freshsales, Insightly, Zendesk Sell Building a Zap 1. Create a Zapier account and search for PersistIQ as a trigger or action app. 2. Authenticate with your PersistIQ credentials or API key. 3. Choose the trigger (something happened in PersistIQ) or action (do something in PersistIQ). 4. Map fields between the two apps. 5. Test with sample data before enabling on real prospects. Design tips - Keep one job per Zap — complex branching is fragile. - Guard against loops: if PersistIQ writes to an app that writes back to PersistIQ, you can create runaway automation. - Test the opt-out path explicitly: whatever flow adds prospects must respect opted-out records.

Last updated on Nov 13, 2026