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.
target_count → company_name, domain, profile_url
Open play page
business_name, domain, city → email, email_source, candidates
Open play page
domain, company_name → company_name, company_domain, company_linkedin_url
Open play page
hq_locations, industries, employee_min → companies_dataset, count, requested_limit
Open play page
Tell us which data provider, dataset, or workflow tool you need next. We will review it for the Deepline roadmap.
Google Sheets appears in 23 Deepline Claude Code workflows for crm data use cases. Connect BounceBan to Google Sheets through Deepline. Run verify bulk with pilot rows, guardrails, and deployable workflow steps.
CrustData V2 appears in 19 Deepline Claude Code workflows for waterfall workflow use cases. Connect CrustData V2 to Salesforce through Deepline. Run job search with pilot rows, guardrails, and deployable workflow steps.
LinkedIn Ads Audiences appears in 17 Deepline Claude Code workflows for outbound tools use cases. Connect LeadMagic to LinkedIn Ads Audiences through Deepline. Run email finder with pilot rows, guardrails, and deployable workflow steps.
Email finder and verification tool popular in the GTM engineering community. Pay-per-use pricing model.
LinkedIn Sales Navigator appears in 14 Deepline Claude Code workflows for linkedin outreach use cases. Connect LinkedIn scraping + Lemlist to Deepline, chat with Claude to scrape a post's commenters, resolve emails via waterfall, and drop into a Lemlist sequence with a personalized first line.
Prefer run-task/search/extract primitives and avoid monitor/stream complexity for agent workflows.
Resolve campaign IDs first, then batch inserts and confirm campaign stats after writes.
RB2B appears in 6 Deepline Claude Code workflows for intent data use cases. Route RB2B's de-anonymized visitor webhooks through Deepline into HubSpot as new or updated Contacts with a web-visit timeline. Fires HubSpot workflows on first identification.
Use for funding data, company intelligence, and founder research. entity_id is the Crunchbase permalink (e.g. \"stripe\" from crunchbase.com/organization/stripe).
Use for SEO/traffic signals — high organic traffic or ad spend = healthy marketing budget = strong prospect. domain_overview first, then keywords for detail.
AI-powered waterfall enrichment platform aggregating data for accurate contact information.
Use for LinkedIn → email/phone enrichment. Run contactout_check_email_status first (free) to confirm data exists before spending credits on enrich.
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.
Web scraping, crawling, search, and AI extraction. Use firecrawl_scrape for single pages, firecrawl_search for web search + scraping, firecrawl_map for URL discovery, firecrawl_crawl for multi-page crawls, firecrawl_extract for structured extraction.
Phone data provider focused on mobile number accuracy. Growing player in the phone waterfall ecosystem.
Google Search is wired into Deepline with 1 available actions.
Multi-source email finder that aggregates results from multiple databases. Competitive pricing.
Use for creating/updating issues, listing team issues by state/priority. Get team IDs with list_teams first, then create/list issues in specific teams.
Use for LinkedIn → email/phone enrichment. Set enrichment_level: \"partial\" for emails, \"full\" for emails+phones. Accepts Sales Navigator URLs unlike ContactOut.
Use channel-native ad endpoints first, then synthesize cross-channel insights. Keep domains normalized and remember Adyntel bills per request except free polling endpoints.
Real-time enrichment and phone data provider. Often used as first step in phone number waterfall sequences.
Generic HTTP Webhook appears in 2 Deepline Claude Code workflows for waterfall workflow use cases. When a HubSpot Contact's field changes, trigger a Deepline workflow that enriches, validates, and routes downstream. Same pattern as Clay webhooks but with Deepline's waterfall pricing.
IPQualityScore appears in 2 Deepline Claude Code workflows for email verification use cases. Run every email through IPQualityScore's deliverability check before importing into Instantly. Deepline chains the gate + import in one prompt.
Trestle appears in 2 Deepline Claude Code workflows for phone data use cases. Connect Trestle and HubSpot to Deepline, chat with Claude to validate phone numbers and caller IDs, then upsert results into HubSpot Contacts.