Refactor GM Scraper Core

@mascotindia123

Hello, I’ve carefully read your complete requirements, and it would be an honor to work with you on refactoring GM Scraper into a scalable browser automation core. With 14+ years of experience in Node.js, Express, Angular, Playwright, REST APIs, webhooks, and queue-based architectures, I can redesign the platform with a clean, modular, and future-ready foundation. I will refactor the backend, database, and Angular UI, implement the Facebook adapter, task queue/worker system, REST APIs, webhooks, StackPosts integration, and complete documentation with smooth migration support. The solution will be delivered milestone by milestone with clean code, GitHub commits, demo videos, screenshots, and thorough testing to ensure seamless deployment. Please check my profile to see my reviews and ratings from satisfied clients, reflecting the quality and reliability of my work. I look forward to discussing your project and building a robust, extensible automation platform. Warm regards, Harpreet Singh

@kabirchy

Hi there, I understand you need to refactor the GM Scraper into a versatile browser automation tool. Your goal to transition from a Google Maps-focused application to one that accommodates Facebook tasks as a first step is an exciting venture. To address this, my approach will involve redesigning the core architecture to make it adaptable and scalable for multiple APIs and web interactions. We'll begin by analyzing the current codebase to identify components that are tightly coupled with Google Maps. I'll then refactor these components to create a flexible and reusable core. Implementing modular services will allow the integration of various web tasks, starting with Facebook. Utilizing Angular for the frontend, Node.js, and Python for backend tasks ensures efficient processing and execution. I'll also design REST APIs to communicate seamlessly between services, ensuring a robust and maintainable system architecture. Let's work together to create a powerful and adaptable browser automation tool that scales with your agency’s growing needs. Best Regards, Khorshed Alam, RS Software

@giaphung2k1

Hello Your local AI lead generation script is likely hitting API bottlenecks or running too slowly to scale your pipeline. I can refactor the codebase to clean up the data processing, optimize the prompts, and make the architecture modular. I recently optimized a similar local GPT-based scraper, cutting runtimes by 40% and lowering API costs. Could you share the current repository so I can take a look? Giáp Văn Hưng

@krupnovdenis

Hello! We can help turn this into a reusable browser automation core with the first Facebook adapter. 1. Which part should we prioritize first: the core platform or the Facebook adapter? 2. Do you already have the current codebase and database schema available for review? — About us We are dZENcode – a full-cycle IT company for digital product development: from design and programming to integrations and post-release support. We build projects from scratch and also work on existing solutions that need further development, improvements, or technical support. You can find detailed information about our services and rates on our official website: https://dzencode.com. Please review it – after that, we can discuss the details and agree on the next step. ⚠️ After clarifying all details, we will define the scope, the suitable cooperation format – task-based, outsourcing, or outstaffing – and the final cost. Projects are guaranteed to reach release with us: • 10+ years providing IT services; • 90+ in-house specialists; • 250+ public reviews since 2015; • We support products under SLA after launch; • We work under NDA and a company contract!

@freelancerimra59

I am 100% confident in refactoring your GM Scraper into a highly scalable, generic browser automation core. I specialize in Node.js, Angular, and Playwright/Crawlee, and have extensive experience transitioning legacy monolithic scripts into modular, worker-based architectures with robust queuing, state transitions, and structured logging. I will build the agnostic core, update the database schema, and deliver the Facebook Tasks adapter alongside the REST API, Webhooks, and StackPosts connector. My architecture will ensure that future platform adapters can be integrated seamlessly without altering the core foundation. Regarding the new execution model, do you have a preferred task queue system in mind (such as BullMQ or RabbitMQ) for handling the Facebook task workers, or should I propose the most efficient stack for your current Node environment?

@FizzaNadeemK

This is fundamentally a platform rewrite disguised as a refactor, and the main risk isn’t Playwright or Facebook integration — it’s separating execution logic from platform-specific assumptions that are already embedded in GM Scraper. The key architectural shift is treating browser automation as a task orchestration system rather than a scraping pipeline, where everything flows through a queue-based execution engine with immutable Task Runs, and Facebook becomes just the first adapter plugged into a neutral core. If done correctly, the system stops thinking in terms of “Google Maps scraping” entirely and becomes a modular execution runtime where Angular only manages state visibility, Node handles orchestration, and Playwright workers execute isolated, retryable tasks with full artifact capture and auditability. The critical success factor here is defining a clean boundary between Core Engine, Platform Adapters, and Execution Workers before touching Facebook, otherwise you end up with another tightly coupled scraper with renamed modules. Are you currently running Playwright in a single-process flow, or do you already have any form of queue/worker separation in the existing GM Scraper codebase? Best regards, Fizza Nadeem K

@mattafareed4848

Hello I have experience with Node.js, Express, Angular, Playwright, REST APIs, and scalable browser automation architectures. I can refactor your Google Maps-specific application into a reusable automation core with a modular Facebook adapter, task queue, webhooks, API integration, and clean documentation while maintaining a scalable, maintainable codebase. Regards Muhammad

@muneeb6767

Your project aligns well with my experience in Node.js, Angular, Playwright, browser automation, REST APIs, and scalable system architecture. I can refactor the existing Google Maps scraper into a modular browser automation core with a reusable adapter system, worker queues, webhooks, and a Facebook integration while keeping the codebase clean, extensible, and production-ready.

@masummsnr

Hi, You want GM Scraper reshaped from a Google Maps tool into a neutral browser automation core, with Facebook as the first adapter on top. The real work sits in the schema rename (platforms, task_runs, artifacts...) and moving off the cron runner to a queue/worker flow with retries, statuses, logs and screenshots. My read: keep Playwright/Crawlee, wrap each platform behind a Task Template + adapter interface so Facebook is the first module, not a patch. Then layer REST API, Webhooks and the StackPosts connector on that core. I work in Node/Express, Angular and REST APIs, and I read code before touching it, so the refactor stays clean. Given the budget, I'd scope Project 1.a first: generic core plus the Facebook adapter and worker flow, delivered to a GitHub repo with a short demo video and migration notes. Question: is the current Playwright execution already isolated per run, or tangled into the Maps cron logic? Regards, Nurullah Al Masum

@shakilan4

Hi, I have strong experience with Node.js/Express, Angular, Playwright, browser automation, REST APIs, webhooks, queue-based workers, and database refactoring. I can refactor your GM Scraper into a generic browser automation core, implement Facebook as the first adapter, and build the task runner, REST API, webhooks, StackPosts connector, and updated admin UI with a modular architecture ready for future platform expansion. Best regards, Shakila Naz

@ffulb

Refactoring PlaywrightCrawler from Google Maps-specific to a generic task runner is mostly about abstracting the scraping logic into platform adapters while keeping your auth and persistence layer intact. I've done similar work converting monolithic scrapers into modular automation cores — the trick is designing clean interfaces between the browser engine and the task modules so adding Facebook or other platforms later doesn't require touching core code. I'd start by auditing your existing GM Scraper structure to map out what stays in core versus what moves into a Google Maps adapter, then build the Facebook module as proof the new architecture works. You can see some related automation work at ffulb.com. Would need access to the current codebase and deployment setup to confirm the cleanest refactor path and get moving.

@AndrewJSMAN

I’ve refactored monolithic scrapers into modular browser automation platforms before—last year converted a Google Maps-specific lead scraper into a generic task executor with Facebook and LinkedIn adapters. This is right in my wheelhouse. I’ll strip all Google Maps references from the codebase, rebuild the DB schema around neutral entities (Platform, PlatformAccount, TaskTemplate, TaskRun, Artifact), and wire the Angular UI to generic controls. The Node/Express core will adopt Crawlee’s task queue with Playwright workers for retries, timeouts, and artifact capture. REST endpoints and webhooks will follow the existing API patterns, then integrate StackPosts via a dedicated connector. I’ll migrate data in stages, validate with sample Facebook tasks (account auth, post scraping, media upload), and push a clean branch to GitHub with setup scripts and rollback paths. I can start immediately.

@securetechs

Hi, sounds like the GM Scraper core has grown into one tangled script over time, that's usually why lead automation tools get hard to extend or wire into a clean API layer down the road. I'd start by pulling the current scraper (PHP/Python) into a staging branch so nothing on your live setup breaks while I work. Then I'd split the core into clear modules, one for scraping/parsing the GM data, one for normalizing and storing leads, and one exposing clean REST endpoints so your Angular frontend or any Node.js services can call it without touching scraper internals directly. Once that's split out, I'll run the refactored core against your existing lead sources side by side with the old output to confirm nothing breaks or drops before handing it over, plus a short doc on the new structure. Timeline is about 3 days for a clean refactor given the scope. Is the current core mostly PHP, mostly Python, or a real mix of both right now, and does the REST API layer already exist or is that part of what needs building in this refactor? Regards, Imtiaz, SecureTechs

@engruhulajom

Hello Dear, I’m Md Ruhul Ajom. I’m a Full-Stack Web & Mobile App Developer with 10+ years of hands-on experience building everything from business websites to complex systems, including CRM, dashboards, chat apps, and delivery platforms. I have completed my B.S.C Engineering in Computer Science and Engineering (CSE) from BUET. How Can I Help You 1. Build your project from scratch or improve existing systems 2. Develop fast, responsive, and modern UI 3. Create a secure backend with clean architecture 4. Integrate APIs, payment systems, and third-party services 5. Optimize performance for better speed and scalability Core Skills Frontend: HTML, CSS, Bootstrap, Tailwind, JavaScript, Vue.js, React.js Backend: PHP (Laravel), Python, Ruby on Rails, C#, Rust Mobile Apps: React Native, Swift, Kotlin Database: MySQL & SQL-based systems Tools: Git, Docker, Linux What Makes Me Different? 1. I focus on real business results, not just code 2. I communicate clearly and respond quickly 3. I deliver clean, maintainable, production-ready work 4. I respect deadlines and project goals If you want a developer who understands both technical execution and business impact, let’s talk. I’m ready to start and discuss your project in detail. Best regards, Md Ruhul Ajom

@novalitztech

Hi, Novalitz Tech here! I see you’re looking to transform the GM Scraper into a versatile browser automation core, moving away from its Google Maps roots. This is a great step towards building a more flexible platform. I would begin by assessing the existing architecture and identifying areas that need refactoring, ensuring we maintain the core functionalities while making it adaptable for future modules. With strong experience in Node.js, Angular, and browser automation through Playwright, I can effectively create a robust backend and a user-friendly admin interface. I’ll focus on implementing a solid task queue system for efficient execution and logging, which aligns well with your goals for scalability and modularity. I’m committed to delivering clean, reusable code that meets your specifications. Reliable communication and thorough documentation will be paramount throughout the process. Best regards, Novalitz Tech

@nutankumarftp

As a seasoned full-stack developer with more than 10 years of experience, I believe that I am well-suited to undertake the complex task of transforming your GM Scraper into a versatile browser automation core. My broad skill-set including Angular and Node.js, aligns perfectly with the technological bases you want to maintain. Additionally, I have proven experience designing and building APIs, as well as implementing robust database schemas all tailored to meet specific client needs - qualities that will be invaluable in refactoring your back-end and database schema. The overreaching architectural changes you desire - moving from specific to generic concepts - resonates deeply with my problem-solving capabilities. Being familiar with RESTful API design patterns means I am comfortable leveraging such system to implement task queueing, worker-based execution, structured logs, timeouts handling etc. My experience in not only understanding but executing these complex platforms means I can readily deliver a final product aligned with your vision of a generic platform. Moreover, my drive for efficient and maintainable code ensures that my work stands the test of time while facilitating future expansions like connecting with StackPosts. Finally, my dual expertise across different development tastes in various industries will bring to bear new perspectives for your project making our partnership all the sweeter. Trust me to make your vision a reality.

@muhammadsaad90

Hi, I can turn your GM Scraper into a clean, modular browser automation platform instead of a Google Maps–only tool. My approach is to refactor the core into a generic task system (tasks, runs, logs, artifacts) powered by a proper queue/worker setup with Playwright. Facebook Tasks will be the first adapter, handling accounts, posts, media uploads, and basic page data to validate the new architecture. The Angular panel will be simplified into a general admin dashboard for accounts, tasks, runs, webhooks, and integrations. I’ll also add REST APIs, webhooks, and a StackPosts connector without locking the system to any single platform. If this sounds aligned, I can start with a quick architecture breakdown and migration plan for your approval. Best Regards, Muhammad Saad K

@alizashaikh8778

As a versatile web and app developer, I am well-positioned to take on your project to refactor the GM Scraper Core into a generic browser automation platform. My solid understanding of Node.js/Express and Angular, which are the technologies that your project heavily leans on bind well with your technological base in a way that helps me contribute from day one without much ramp-up time. Having worked on similar projects in the past, I understand the importance of the task at hand and would approach it with utmost professionalism. My years of experience in website and application development have made me proficient in adapting to varying technology requirements. This skill will be crucial as I revamp the architecture centered around neutral concepts - Platforms, Browser Profiles, Task Templates, Execution Logs, and Integration Connectors - while focusing on avoiding existing Google Maps specificity. Additionally, my ability to think holistically about platforms will keep us from falling into a StackPosts-only integration. Rest assured, under my collaboration-based model of work, you can expect clear communication, commitment to quality, and effective support throughout the project involvement. So let’s turn GM Scraper into a powerful digital execution product together!

@nicolasalexandro

I have experience refactoring complex AI-driven automation tools like your GM Scraper core. I understand your goal is to streamline local lead generation for marketing agencies. I’ve worked on similar projects enhancing code efficiency and scalability while maintaining AI accuracy and responsiveness. My approach includes thorough code review and incremental improvements for stability. Happy to review your current setup and get this back to a stable state.