Website Tech Stack & CRM Signal Detector — Apify Actor

Detect public website CRM, MarTech, analytics, ecommerce, ads, workflow, payment, and site-builder signals for Clay, HubSpot, Salesforce, Apollo, Pipedrive, RevOps, GTM, and AI-agent enrichment workflows.

This Actor turns public company website HTML/text into flat company-level rows such as detected CRM, analytics tags, ecommerce stack, automation tools, payment tools, score, segment, and recommended RevOps action. It is designed as a lightweight technology stack detection API and CRM enrichment API, not a contact scraper.

It does not harvest emails, phone numbers, people, LinkedIn profiles, or login-wall data.

Fast buyer workflow

1. Paste public company website URLs from a CRM export, Clay table, Apollo account export, HubSpot/Salesforce/Pipedrive list, Google Sheet, or AI-agent workflow.
2. Run sample mode first, then URL mode for a small batch.
3. Export detected_technologies, technology_categories, crm_platforms_detected, analytics_detected, ecommerce_detected, tech_signal_score, and recommended_action to your CRM/table.
4. Use your own approved CRM/contact-data provider only after the account passes your stack/ICP gate.

The output is intentionally flat JSON so it works in Apify API calls, MCP/AI-agent tools, Clay, HubSpot, Salesforce, Pipedrive, Apollo, Airtable, Google Sheets, Zapier, n8n, Make.com, and CSV workflows without custom parsing.

Buyer use cases

Use this Actor when you need quick public website technology signals:

• enrich company/account records with public CRM and MarTech stack hints;
• identify accounts using HubSpot, Salesforce, Pipedrive, Zoho, Segment, GA4, GTM, Shopify, WordPress, Webflow, Intercom, Calendly, Stripe, PayPal, Zapier, n8n, or Make.com;
• prioritize RevOps, GTM, agency, integration, and sales-tech prospects;
• route ecommerce, analytics, ads, CMS, and workflow signals into Clay/CRM fields;
• screen websites before deeper paid enrichment.

Search terms this Actor is designed to satisfy: technology stack detection, website tech stack API, company tech stack enrichment, domain technology detection, CRM enrichment API, CRM tech stack detection, MarTech detection, sales intelligence API, RevOps research API, GTM account research, HubSpot enrichment, Salesforce enrichment, Pipedrive enrichment, Apollo enrichment, Clay company enrichment, website analysis lead generation, ecommerce stack detection, Shopify detection, WordPress detection, Webflow detection, Google Tag Manager detection, GA4 detection, Segment detection, Intercom detection, Zapier enrichment, n8n enrichment, Make.com workflow enrichment, MCP, AI agents, x402, agentic payments.

Copy-paste API quickstart

Apify API callers can run a sample synchronously:

curl -X POST "https://api.apify.com/v2/actors/jorokotev~public-website-tech-stack-crm-signals/run-sync-get-dataset-items" \
  -H "Authorization: Bearer ***" \
  -H "Content-Type: application/json" \
  -d '{"source":"sample","maxResults":3}'

AI-agent and MCP buyers can also probe Apify's x402 payment flow when enabled by Apify for the Actor/account. A no-auth call should return payment requirements rather than free data:

curl -i -X POST "https://api.apify.com/v2/actors/jorokotev~public-website-tech-stack-crm-signals/run-sync-get-dataset-items" \
  -H "X-APIFY-PAYMENT-PROTOCOL: X402" \
  -H "Content-Type: application/json" \
  -d '{"source":"sample","maxResults":1}'

Example input — live URL mode

{
  "source": "urls",
  "startUrls": [
    {"url": "https://example.com"}
  ],
  "targetCategories": ["crm", "marketing_automation", "analytics", "ads_and_retargeting", "ecommerce", "cms_and_site_builder", "workflow_and_sales", "payments"],
  "minTechSignalScore": 0,
  "maxUrls": 10,
  "maxResults": 10,
  "timeoutSeconds": 10,
  "maxBytes": 300000,
  "respectRobotsTxt": true,
  "includeErrorRows": false
}

Output fields

• company, url, page_title
• http_status, fetch_status
• tech_signal_score, crm_fit_segment
• detected_technologies, technology_categories, detected_by_category
• crm_platforms_detected, marketing_automation_detected, analytics_detected, ecommerce_detected, workflow_and_sales_detected, payments_detected
• evidence_markers
• recommended_action, integration_notes
• risk_flags, automation_note
• redacted_text_excerpt, observed_at, source_mode

Data and privacy policy

• Public website URLs only.
• Company-level technology analysis only.
• Emails, phone numbers, social profile URLs, and simple person-role hints are redacted from text excerpts.
• No contact harvesting or contact export.
• No LinkedIn/login-wall/profile scraping.
• URL mode fetches only user-supplied URLs; it is not an open-ended crawler.
• URL mode blocks localhost, embedded credentials, cloud metadata hosts, private/link-local/reserved IPs, and redirects to non-public addresses before fetch.
• robots.txt is respected by default.

Apify monetization posture

The intended Apify-only monetization path is PPE:

1. Use Apify's synthetic default dataset item event (apify-default-dataset-item) for per-result charging.
2. Keep strict caps: maxUrls <= 50, maxResults <= 50, per-URL timeout <= 30s, max bytes <= 300 KB.
3. Do not add custom Actor.charge() events in code; per-result billing should come from Apify's automatic dataset-item synthetic event to avoid double-charging or charge-without-row edge cases.

Local checks

cd /home/hercules/hermes-workspace/deep-research/apify-hermes-passive-income-20260704/templates/public-website-tech-stack-crm-signals-actor
python3 -m py_compile src/lead_fit.py src/tech_stack_signals.py src/main.py tests/conftest.py tests/test_tech_stack_signals.py
PYTHONPATH=. uvx --with pytest pytest -q
PYTHONPATH=. python3 -m src.main
APIFY_CLI_DISABLE_TELEMETRY=1 apify validate-schema