Terraform Provider Vendor Leads Scraper avatar

Terraform Provider Vendor Leads Scraper

Pricing

from $6.00 / 1,000 leads

Go to Apify Store
Terraform Provider Vendor Leads Scraper

Terraform Provider Vendor Leads Scraper

Scrape Terraform Registry to find B2B infrastructure companies that publish Terraform providers. Returns namespace, provider name, tier, download count, GitHub repo, registry URL, and publish date. Perfect for DevRel, cloud vendor outreach, and DevOps tooling sales.

Pricing

from $6.00 / 1,000 leads

Rating

0.0

(0)

Developer

GoCreative AI

GoCreative AI

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 hours ago

Last modified

Share

Scrape Terraform Registry to find B2B infrastructure companies that publish Terraform providers. Returns namespace, provider name, tier, download count, GitHub repo, registry URL, and publish date. Perfect for DevRel, cloud vendor outreach, and DevOps tooling sales.

No API key, no signup, no subscription — pay only for what you scrape. Clean, structured output ready for CSV, JSON, Excel, or direct API export into your own pipeline.

What this scraper does

Scrape Terraform Registry to find B2B infrastructure companies that publish Terraform providers. Returns namespace, provider name, tier, download count, GitHub repo, registry URL, and publish date. Perfect for DevRel, cloud vendor outreach, and DevOps tooling sales.

Every run pulls fresh data straight from the source and pushes clean, typed records to the dataset — ready for your CRM, spreadsheet, AI agent, or data pipeline.

Use cases

  • B2B lead generation — build targeted prospect lists with verified, structured data
  • Sales prospecting — find companies and contacts that match your ICP
  • Market research & competitive intelligence — track an industry or niche in structured form
  • AI agents & automation — feed agents clean external data without scraping infra
  • Data enrichment — append fresh fields to your existing lists

Input

FieldDescription
tierWhich tier(s) of providers to return. 'official' = HashiCorp-owned, 'partner' = verified tech partners, 'community' = open-source publishers
maxResultsMaximum number of provider records to return (1–500).
keywordOptional search keyword to filter providers by name or description (e.g. 'aws', 'kubernetes', 'database').
fetchDetailsIf enabled, makes a second request per unique namespace to retrieve full description and latest version. Slightly slower but richer output.

Output

Every result is a clean structured record. Export the full dataset as CSV, JSON, or Excel from the Apify console, or pull it via the Apify API straight into your own tools.

Why use this actor

  • Scrape terraform provider vendor leads — fast, structured, reliable.
  • Terraform provider vendor leads data export (csv, json, excel) — fast, structured, reliable.
  • Terraform provider vendor leads api alternative — no key required — fast, structured, reliable.
  • Automated terraform provider vendor leads monitoring on a schedule — fast, structured, reliable.
  • Structured terraform provider vendor leads records for ai agents and pipelines — fast, structured, reliable.

How it works

This actor pulls data directly from the source, structures it into clean rows, and pushes each result to the dataset. It runs on Apify's infrastructure — reliable, schedulable, and pay-per-result so you only pay for data you actually get.

Pricing

Pay-per-result via the Apify Store. No monthly subscription, no minimums — run it once or schedule it daily; you're only charged for the results returned.

FAQ

Do I need an API key or account? No. Just provide your input and run it.

Can I schedule it to run automatically? Yes — use Apify Schedules to run it hourly, daily, or weekly and get fresh data on autopilot.

What formats can I export? CSV, JSON, Excel, or via the Apify API.

Can I integrate it into my own app? Yes — call it via the Apify API and pull results directly into your pipeline.

Is the data accurate and fresh? Data is pulled live from the source on each run, so it reflects what's available at run time.