Dealership New-Listing Alert Engine - 21/04/2026 15:43 EDT

@diektech

Hi, This is Elias from Miami. I checked your project description and understand you’re looking to build a web-based tool that helps auto dealerships quickly identify newly posted vehicles. I’ve worked on several similar platforms and understand the key technical challenges involved. I’d be happy to discuss the project and suggest the best technical approach. I have a few questions to get a better understanding: Q1 – What specific user roles do you envision for the dealerships? – Q2 – Are there any existing systems you want to integrate with this tool? – Q3 – How do you plan to handle notifications for new listings? Looking forward to hearing from you.

@Herculesz

Hi Thanks for the invitation! I have strong experience building real-time monitoring and alerting systems that ingest listings from multiple sources, normalize the data, and trigger fast notifications through email, SMS, or webhooks. The main technical challenge here is keeping alert latency under 60 seconds while handling different marketplace structures, private-seller sites, and frequent content changes without making the scraper layer brittle. I would solve that with a modular crawler/connector architecture, a rules engine for make, model, year, mileage, and price filters, and an event-driven alert pipeline designed for fast matching and delivery. I can also build a simple rules screen or config-based admin layer so criteria can be updated without touching code, while keeping the webhook JSON and email outputs clean and consistent. The repo would be Dockerized, documented, and structured so future modules like price-drop or competitor-action alerts can be added without rewriting the core engine. Thanks, Hercules

@teodorgeorge

Hello, I can help you build a fast and straightforward alert engine that detects new vehicle listings across marketplaces and sends notifications in under a minute. I’ve worked with similar real‑time flows, so setting up clean rules, webhook payloads, and a Dockerised repo should be smooth. The structure will stay simple but flexible so you can expand into price‑drop or competitor alerts later without reworking the core. Thanks, Teo

@AZTURK1

Hi there, I will build a real-time New-Listing Alert Engine that watches marketplaces and private-seller sites for matching make/model/year/mileage/price and delivers email, SMS, or webhook notifications with <60s average latency; my background in Docker, Python scraping, PHP/Node webhook endpoints and low-latency pipelines makes me a fit. - Implement ingest adapters (Python async scrapers + marketplace APIs) and a rules UI or JSON config to define make/model/year/mileage/price filters - Deliver a low-latency matching pipeline (Redis pub/sub or Kafka lite), immediate notifier (SMTP, Twilio SMS, webhook endpoint) and sample CRM webhook JSON + human-readable email templates - Dockerised repo, README with environment variables, and unit + integration tests for latency verification - Risk/quality-control: staged deployment with backup checkpoint and post-deploy validation tests to ensure <60s delivery Skills: ✅ Python ✅ Docker ✅ API Development ✅ MySQL ✅ Low-latency pipelines / Redis pub/sub ✅ SMTP / Twilio integration Certificates: ✅ Microsoft® Certified: MCSA | MCSE | MCT ✅ cPanel® & WHM Certified CWSA-2 I’m available to start immediately. Is this already running on a live production server or do you want a staged rollout for testing? Best regards,