expired-leads

Expired Leads Reactivation

Week 1 build. FUB setup, REDX sync, 4,760-lead CSV import, and enrichment.

Local setup

python3.11 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env  # fill in credentials
pytest

Run the one-time import

python -m src.import_csv data/vortex_redx.csv

Run enrichment

python -m src.enrich_leads

See docs/ for manual setup checklists (FUB, REDX sync, acceptance).

Railway deploy

1. Push repo to GitHub (tirzo-gif/expired-leads).
2. In Railway, New Project > Deploy from GitHub. Select the repo.
3. In Variables tab, paste every key from .env.example with real values (including SUPABASE_SERVICE_KEY, FUB_API_KEY).
4. Under Settings > Deploy > Start Command, set to python -m src.enrich_leads for scheduled runs.
5. Create a scheduled trigger: Settings > Cron Schedule, 0 4 * * * (daily 4am UTC).
6. Historical one-time CSV import is run manually once: railway run python -m src.import_csv data/vortex_redx.csv (upload the CSV to the Railway volume first).