Clutch IT Agencies Lead Generator

Generate B2B leads from clutch.co: collect companies from a Clutch category, visit each company’s website, and extract an email from the company website (not from Clutch).

You control what is required to push an item to the Dataset via requiredFieldsForOutput.

What it does

• Clutch directory pages: collects company profile URLs (pagination supported)
• Company profile pages (Clutch): extracts basic fields (name, location, services, website, phone, LinkedIn — best effort)
• Company website crawl: crawls homepage + common pages and searches for emails via mailto: and regex up to emailDepth
• Output: pushes items to the Dataset when all fields from requiredFieldsForOutput are non-empty

What it does NOT do

• Multiple categories, enrichment, email verification APIs, “anti-bot bypass”
• Guaranteed emails for every company (many companies hide emails behind forms)

Requirements / notes

• Clutch often returns 403 without a proxy. For reliable runs, enable Apify Proxy in proxyConfiguration.
• Respect ToS/robots and use reasonable limits (maxCompanies, emailDepth).

Input

The Console form is defined in .actor/input_schema.json.

• startUrls (required): Clutch category URLs
  • example: https://clutch.co/directory/web-developers
• maxCompanies: maximum number of companies to process
• countryFilter: list of allowed countries (empty array = no filter)
• extractEmails: enable email extraction from company websites (should be true for lead generation)
• emailDepth: website crawl depth
  • 0: homepage only
  • 1: homepage + common pages (contact/about, etc.)
  • 2-3: deeper (can be slower)
• requiredFieldsForOutput: which fields must be present to push an item to the Dataset
  • default: ["company_name","company_website","industry","source_url"]
  • add "email" if you want to push only leads with emails
• proxyConfiguration: proxy settings (recommended: useApifyProxy: true)

Example INPUT:

{
  "startUrls": [{ "url": "https://clutch.co/directory/web-developers" }],
  "maxCompanies": 200,
  "countryFilter": [],
  "extractEmails": true,
  "emailDepth": 1,
  "requiredFieldsForOutput": ["company_name", "company_website", "industry", "source_url"],
  "proxyConfiguration": { "useApifyProxy": true }
}

The Actor stores items in this shape (some fields may be empty depending on requiredFieldsForOutput):

{
  "company_name": "Twin Sun",
  "company_website": "https://twinsunsolutions.com",
  "email": "sales@twinsunsolutions.com",
  "phone": "(615) 873-0035",
  "country": "United States",
  "city": "Nashville",
  "services": ["Web Development", "Custom Software Development"],
  "industry": "IT / Software",
  "linkedin_url": "https://www.linkedin.com/company/twinsunllc/",
  "source": "clutch.co",
  "source_url": "https://clutch.co/profile/twin-sun"
}

How email extraction works (short)

• First, it checks mailto: links and visible emails in HTML
• Then it follows a limited set of internal links (typical paths like contact/about/team) up to emailDepth
• Emails are validated with a simple regex and deduplicated

Troubleshooting

• I get 403 from Clutch:
  • enable proxyConfiguration.useApifyProxy: true
  • reduce load: lower maxCompanies, keep emailDepth ≤ 1
• Dataset is empty:
  • if you included "email" in requiredFieldsForOutput, the Actor will skip companies where email cannot be found (forms only)
  • verify extractEmails: true when requiring emails
• Too slow:
  • reduce maxCompanies
  • set emailDepth: 0 or 1