Example input
{
"start_urls": [
{ "url": "https://northstar.example" },
{ "url": "https://harborworks.example" }
],
"max_pages_per_site": 5,
"extract": ["company_name", "emails", "phones"],
"delivery": "CRM-ready CSV"
}All workflows
ConfiguredData Collection
Structured Business Data Extractor
Turn approved public company websites into reviewable records containing company identity, contact details found on-site, source pages, and processing status.
No access or payment before scope confirmation
Your input
Tell us what to run. We handle the operating structure.
You do not need to prepare technical configuration. Provide the business requirements, examples, and approved access; we translate them into fields, rules, and a tested schedule.
What you provide
- Public website URLs
- Required contact and company fields
- Maximum page depth or page types
- Exclusion rules
- Delivery destination
- Optional review criteria
How you provide it
- Setup form
- CSV or spreadsheet URL list
- Approved database export
- Example output schema
- Written domain and exclusion rules
The result
What this workflow delivers.
A structured company table ready for CRM review, research, profiling, or downstream data work, with found and not-found states kept explicit.
Best for: CRM and RevOps teams, researchers, analysts, founders, operators, and data teams building company datasets from approved public websites.
Sources
- Customer-provided public website URLs
- Public home pages
- Public contact pages
- Public about pages
- Other approved public pages within the agreed domain scope
Output fields
- Company name
- Canonical website
- Email addresses found
- Email status
- Normalized phone numbers found
- Phone status
- Pages checked
- Crawl status
- Review status
- Collection timestamp
Delivery options
- Google Sheets
- Excel
- CSV
- JSON
- CRM-ready import table
- Database-ready table
Operating scope
- Agreed website batch and page depth
- On demand, weekly, or monthly
- Public sources
Worked example
See what goes in and what comes back.
Examples show the delivery structure before setup. Names and values are illustrative, not client records or performance claims.
Example delivery
Illustrative record{
"company_name": "Northstar Components",
"website": "https://northstar.example",
"emails": ["hello@northstar.example"],
"email_status": "found",
"phones": ["+1 202 555 0147"],
"phone_status": "found",
"pages_checked": [
"https://northstar.example",
"https://northstar.example/contact"
],
"crawl_status": "completed",
"review_status": "review",
"collected_at": "2026-08-19T09:00:00Z"
}Installation path
From source approval to scheduled operation.
The first representative run is reviewed before the workflow becomes a recurring operation.
Provide an approved website list and required fields
Confirm page-depth and domain rules
Process a representative sample
Review found, missing, and failed states
Approve the delivery structure and schedule
Managed history
Each run adds to a useful operating history.
Each processing run can be timestamped and appended rather than silently replacing earlier observations. Source pages, found and missing states, crawl status, and review status support later comparison.
Retention and portability
Retention is agreed during setup. Records can be exported to CSV, JSON, a CRM-ready table, or a customer-controlled destination. Deletion requirements and any longer-term managed archive are scoped explicitly.
What the accumulated history can support
- Enrich company records before CRM review
- Compare contact-data coverage over time
- Audit which source pages produced a value
- Identify domains that repeatedly fail or return no data
- Build research and company-profiling datasets
Interpretation limits
History makes comparison possible, but it does not remove source limitations or turn signals into guaranteed business outcomes.
01
Works only on approved publicly accessible websites
02
Does not access login-protected pages or bypass CAPTCHAs
03
Coverage depends on website structure and visible content
04
A found address or phone number may be outdated, generic, or unsuitable for a particular use
05
Not-found means no qualifying value was found in the agreed scan, not that no value exists
06
Customers remain responsible for lawful purpose, website terms, and applicable privacy rules
Safeguards
Automation stays inside agreed boundaries.
Access, retention, exports, and operating controls are confirmed for this workflow before launch.
01
Public pages only
02
No login or CAPTCHA bypass
03
Source pages retained with each record
04
Missing values remain explicit
05
Failed URLs and crawl status remain visible
06
Contact data is delivered for customer review, not represented as guaranteed current or deliverable
Related workflows
Continue through the catalogue.
Monitoring · Ready
Search Trend Monitor
Track changes in search interest, regional demand, related queries, and emerging topics without repeatedly checking trend tools manually.
Explore workflow
Monitoring · Configured
EU Funding & Tender Opportunity Monitor
Monitor the European Commission Funding & Tenders Portal for grants and tenders that match your themes, programmes, status rules, and deadline windows.
Explore workflow
Monitoring · Configured
TikTok Content & Trend Monitor
Monitor approved public TikTok profiles, hashtags, keywords, and posts to build a structured view of content, reach, engagement, and emerging themes.
Explore workflow
Request configuration
Configure Structured Business Data Extractor.
Share the sources, rules, and destination. We’ll verify access and confirm the final setup and monthly operating scope.
SetupQuoted after sample
ManagedOptional managed plan
Normally liveConfirmed after sample