Automated QA and Publishing for Lovable Websites

This automation acts as a diligent QA assistant for your lovable.dev projects. Here’s how it works:

1. Initiation: The workflow begins when triggered by an external event (like a webhook from n8n or Zapier), receiving the specific Lovable project buildUrl you want to process.
2. Setup & Navigation: It opens the project in a pre-authenticated browser, automatically handling workspace selection and waiting for the Lovable editor to fully load.
3. Build Verification: The agent intelligently detects if a website generation is in progress or if an unsent prompt needs to be submitted. It waits patiently for any builds to complete, ensuring it's working with the latest version.
4. Pre-QA Cleanup: Before inspection, the agent navigates to the project settings to disable the "Made with Lovable" badge for a clean, professional appearance.
5. Comprehensive QA: It opens a preview of your site and performs a thorough visual QA inspection, checking for critical issues like broken layouts, overlapping elements, non-loading images, and broken sections. It separately assesses desktop and mobile presentation.
6. Automated Correction: If critical, blocking issues are found, the agent doesn't give up. It automatically sends a message to the Lovable chat, describing the problems it found and requesting a fix. It will repeat this QA-and-fix cycle a configurable number of times.
7. Publishing: Once the site passes all critical QA checks, the agent proceeds to publish it live.
8. Reporting: Finally, the automation concludes by providing a detailed report, including the final published URL, a summary of the QA results (pass/fail for different criteria), and a list of all issues it encountered along the way.

Usage Ideas

• Integrate with your CI/CD pipeline by using a webhook to trigger this QA agent automatically after every new commit to your website's main branch.
• Connect to a project management tool (via n8n, Make, or Zapier) to automatically run this QA and publish flow when a development task is moved to a "Done" or "Ready for Deploy" column.
• Set up a scheduled run to periodically QA and republish key landing pages, ensuring they remain high-quality and functional over time.
• Empower non-technical team members by creating a simple form (connected via a webhook) where they can submit a Lovable URL for automated QA and publishing.

Customization Ideas

This template is a powerful starting point, and you can easily adapt it to your specific needs. Here are some of the ways you can customize this automation:

• Define QA Standards: You have full control over what the agent considers a "critical" issue. By editing the analysis prompts, you can teach the agent your team's specific quality bar, ensuring it only flags problems that truly matter to you.
• Control The Fix Cycles: Easily adjust the maximum number of times the agent will try to automatically fix issues. You can increase it for more persistent self-healing or decrease it to conserve lovable.dev build credits.
• Adapt to Your Language: The template can be quickly updated to work with your lovable.dev account's language by changing a few keywords (e.g., from "Einstellungen" to "Settings") in the automation's logic.
• Connect Your Triggers: Start the QA process from your existing tools. You can trigger this automation using a webhook, or via events from services like n8n, Make, or Zapier, allowing it to fit seamlessly into your existing workflows. For example, trigger the QA process whenever a task is moved to "Ready for Review" in your project management tool.
• Target Any Project: Simply provide the buildUrl and workspaceName as inputs to run the same robust QA process on any of your lovable.dev projects.