prospiq launches with HubSpot, Salesforce, Zoho, and the Chrome extension. Zapier and Google Sheets are coming. But if your stack uses something we don't yet integrate with directly — Outreach.io, Salesloft, Pipedrive, Apollo's sequencing layer, a homegrown system — you can still get prospiq's data into it. Here's how.
The three universal workflows
Almost every sales stack accepts data through one of these three paths. If your tool supports any of them, prospiq integrates effectively.
CSV export and import
Every major sales tool accepts a CSV import. Almost all of them.
Workflow:
- Run enrichment in prospiq (single, bulk, or company search)
- Save the verified results to a saved list
- Export the list as CSV
- Import the CSV into your sales tool
This works for: Outreach.io, Salesloft, Pipedrive, Apollo, Reply.io, Mailshake, Lemlist, Smartlead, Instantly, and roughly every other tool in the sales tooling ecosystem.
The downside: it's manual. You're triggering each export-import yourself. For one-time campaigns this is fine. For ongoing workflows, see the API path below.
Webhook from prospiq → your tool
If your sales tool can receive incoming webhooks (most modern ones can), you can set prospiq up to push enriched contacts to your tool in real time. This requires Pro plan API access.
Workflow:
- Configure your sales tool to receive webhooks at a specific URL
- Configure prospiq to fire a webhook when a contact is enriched
- Map the prospiq fields to your tool's expected schema
The actual mechanics depend on what your tool supports — most modern sales platforms have webhook documentation that walks you through their side of it.
API → API integration
If you have engineering resources, the most flexible path is a direct API integration. prospiq's API returns verified contacts in JSON. Your engineer writes a small script that calls prospiq, takes the response, and posts it to your tool's API.
This is the right path when:
- You need transformation logic between prospiq's output and your tool's input
- You want to enrich contacts based on triggers in your CRM (new lead created, lead score crosses threshold, etc.)
- Volume is high enough that manual export-import would be untenable
Specific tool patterns
Outreach.io
Outreach accepts CSV import for prospects. Run enrichment in prospiq, export to CSV, import to Outreach as new prospects in a sequence.
For real-time: use prospiq's API and Outreach's API together with a small middleware script.
Salesloft
Same pattern as Outreach. CSV import for prospects works out of the box. API-to-API integration is the long-term workflow for scale.
Pipedrive
Pipedrive accepts CSV import for both Leads and Contacts. The People object is the standard target for enrichment data. Manual workflow today, Zapier integration when our Zapier app launches.
Apollo (using Apollo for sequencing only)
If you use Apollo's outreach features but want prospiq's data quality, the CSV path works — export from prospiq, import into Apollo as a contact list, sequence from there.
Reply.io, Mailshake, Lemlist, Smartlead, Instantly
All standard cold email platforms. All accept CSV import. The Zapier integration (when launched) will make this real-time for all of them.
Homegrown systems
If your team has built internal sales tooling, the right integration is the API. The integration is usually 50-200 lines of code and lives forever, since prospiq's API is designed for stability across changes.
What we're working on
We prioritize native integrations based on what our customers ask for. If your tool isn't on our roadmap and you'd want to use it with prospiq, tell us what tool you use, what specifically you'd want the integration to do, and how often you'd use it. We don't promise to build every requested integration, but we do read every request and they shape the roadmap.
Bottom line
You don't need a native integration to use prospiq effectively. CSV export covers 90% of real workflows. The API covers the other 10%. The native integrations make the workflow nicer, not possible.