Lead Finder docs
Quick notes on how this prototype works end-to-end.
Routes
- / marketing landing
- /app dashboard
- /app/jobs/new create a job
- /app/jobs/:id run job, view leads, export
- /app/suppression do-not-contact list
- /app/exports export history
- /app/admin scoring + rate limits + crawl policy
How “background jobs” work in this MVP
Anything API routes don’t run as a separate worker process, so jobs run as a series of small “chunks”. The UI calls POST /api/jobs/:id/run repeatedly while the job is in running state.
Connectors
Connectors are in /apps/web/src/app/api/lead-finder/connectors:
- Discovery: Google Places (Text Search + Details)
- Enrichment: website crawl (email/social/pixels)
- Enrichment: domain info via RDAP
Config
This demo expects NEXT_PUBLIC_GOOGLE_MAPS_API_KEY for discovery.
Auth
User Accounts are currently disabled in project settings, so everything runs in a shared demo mode. If you enable User Accounts, we can tie jobs/exports/suppression to real users and lock the Admin area.