Compare coverage, regional fit, API access, and where each tool belongs in a Deepline workflow.
Use provider pages to answer one decision at a time: coverage, workflow fit, API access, cost shape, and the right destination for the data.
Start here when the question is coverage, fallback logic, or which provider fills the gaps another one leaves behind.
Start here when the question is writeback, routing, ownership, or where reviewed data should land.
Start here when the decision is about sequencing, triggering, or what happens after enrichment and review.
Prefer tools with APIs, structured outputs, and testable actions. Use Deepline for enrichment waterfalls and workflow runs. Use CRM and sequencer APIs only after review gates are clear.
These pages connect directly to common GTM workflows, enrichment stacks, and research requests.
All-in-one sales intelligence platform with contact database, enrichment, and outreach. Known for large database but data freshness concerns.
Open provider page
Enterprise CRM and RevOps platform with a large ecosystem, flexible object model, and significant implementation overhead.
Open provider page
All-in-one CRM, marketing, sales, and service platform. Industry standard for SMB and mid-market.
Open provider page
Email and phone finder with large professional database. Direct competitor to Apollo and Lusha.
Open provider page
Web scraping and automation platform with marketplace of pre-built scrapers for LinkedIn, Google Maps, etc.
Open provider page
Dutch-Belgian credit and company intelligence provider, now part of Creditsafe, used for Benelux credit risk, payment behavior, and prospecting data.
Open provider page
Sales intelligence platform focused on human-verified B2B contacts, buyer signals, and enterprise outbound data operations.
Open provider page
Email finder and verification tool popular in the GTM engineering community. Pay-per-use pricing model.
Open provider page
Use notion_get_database first to inspect the schema before creating/updating pages. Always pass Notion-Version header. database_id comes from the URL.
Open provider page
Start with free autocomplete and default to fuzzy contains operators `(.)` for higher recall. Use ISO-3 country codes, prefer crunchbase_categories over linkedin_industries for niche verticals, and use employee_count_range for filtering instead of employee_metrics.latest_count.
Open provider page
SEO and SERP data APIs — keyword search volume, Google/Amazon SERP, technographics, content analysis, and labs datasets.
Open provider page
Category-by-category decision trees for the most-asked GTM categories.
Healthcare data is deeply segmented by use case. The right provider depends on whether you're targeting HCPs for pharma sales, running real-world evidence studies, tracking patient journeys, or doing payer analytics. Here's how to pick:
Global providers (ZoomInfo, Apollo, D&B) have thin coverage outside the US. Regional specialists almost always beat them on accuracy in their home region. Pick by geography:
Retail/CPG data splits into three buckets: scanner/panel data (what's selling), digital shelf analytics (online performance), and shopper behavior (who's buying). Pick based on the channel and question:
These `/p/deepline/*` pages are public play contracts with inputs, outputs, workflow steps, and CLI instructions for running or forking the play.
first_name, last_name, position → icp_tier, icp_reason, icp_qualification_valid
Open play page
linkedin_url, contact_linkedin, current_domain → rows
Open play page
domain, max_items, profile_depth → domain, linkedin_company_url, rows
Open play page
post_url, max_items → rows
Open play page
Tell us which data provider, dataset, or workflow tool you need next. We will review it for the Deepline roadmap.