How tecso-dev/sorinflow-data-mamager works
SorinFlow is a Persian real-estate workspace whose main flow collects Divar listings, stores and enriches property records, then matches opportunities to CRM customers for follow-up. Staff use a role-aware dashboard; customers have a separate portal. The README documents additional collection scheduling, authenticated contact extraction, messaging, AI, and operational integrations. Edges rely on README statements or shown source references; unsampled implementation details are represented only where the README identifies the capability.
Main entry points: match_engine.py Automatic match engine · divar_scraper.py Divar scraper · routes API routers · portal Customer portal
Components 24
Divar collection
- Divar scraper
app/scraper/divar_scraper.py - Divar sessions
app/services/divar_session.py - Scrape queue and schedules
app/services/scrape_queue.py
Property intelligence
- Property inventory
app/models/property.py - Listing reader
app/ai/listing_reader.py - Listing embeddings
app/ai/embeddings.py - Property matching
app/services/match_service.py - Model gateway
app/services/llm.py - Telegram assistant
app/ai/assistant.py
CRM and portal
- Customer portal
frontend-next/src/app/portal - Automatic match engine
app/crm/match_engine.py - CRM workflow
app/crm - Portal request bridge
app/crm/portal_bridge.py
Users and messaging
- Staff dashboard
frontend-next/src/app/panel/(app) - Authentication and permissions
app/auth - SMS and email
app/services
Runtime and integrations
- API routers
app/api/routes - Database and cache
app/database.py - Background supervision
app/services/supervisor.py - Google Cloud export
app/services/gcp/pipeline.py
Other components
- Staff
- Portal visitor
- Divar
- Telegram
Connections 24
- Staff → Staff dashboard: uses
README.md - Portal visitor → Customer portal: uses
README.md - Staff dashboard → API routers: requests
- Customer portal → API routers: requests
- API routers → Authentication and permissions: guards
README.md - API routers → Divar scraper: starts collection
README.md - Divar scraper → Divar: collects listings
README.md - Divar sessions → Divar: authenticates
README.md - Scrape queue and schedules → Divar scraper: dispatches jobs
README.md - Divar scraper → Property inventory: stores listings
README.md - Property inventory → Database and cache: persists in
app/database.py - Listing reader → Model gateway: requests analysis
app/ai/listing_reader.py - Listing embeddings → Model gateway: requests embeddings
app/ai/embeddings.py - Property matching → Listing embeddings: uses similarity
app/services/match_service.py - Automatic match engine → Property inventory: judges listings
app/crm/match_engine.py - Automatic match engine → Property matching: scores matches
app/crm/match_engine.py - Automatic match engine → Portal request bridge: records matches
app/crm/match_engine.py - Automatic match engine → CRM workflow: notifies consultants
README.md - CRM workflow → SMS and email: sends messages
README.md - Customer portal → Portal request bridge: submits requests
- Telegram assistant → Model gateway: uses model gateway
- Background supervision → Scrape queue and schedules: supervises loops
app/services/supervisor.py - Background supervision → Google Cloud export: runs exporter
app/services/gcp/pipeline.py - Google Cloud export → Telegram: exports backups