{"product_id":"apify-crawl-quality-check-before-n8n-chatbot-kb-refresh","title":"Apify Crawl Quality Check Before n8n Chatbot KB Refresh","description":"\u003ch3\u003eBefore you refresh your n8n Chatbot knowledge base, confirm your Apify crawl is actually usable.\u003c\/h3\u003e\n\u003cp\u003eThis \u003cstrong\u003eApify Crawl Quality Check Before n8n Chatbot KB Refresh\u003c\/strong\u003e workflow manually audits a completed Apify crawl run. It verifies the actor run finished successfully, checks the exported dataset for missing required pages and quality failures, then routes \u003cstrong\u003ePASS\u003c\/strong\u003e (you refresh the KB) or \u003cstrong\u003eBLOCK\u003c\/strong\u003e (you keep the current knowledge base) \u003cem\u003ewithout writing to your destination\u003c\/em\u003e.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eManual trigger in n8n\u003c\/strong\u003e to start the quality gate when you’re ready to refresh.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eValidates required configuration\u003c\/strong\u003e: reads your configured Apify crawl \u003cem\u003erun ID\u003c\/em\u003e, \u003cem\u003enamespace\u003c\/em\u003e, \u003cem\u003eexpected URLs\u003c\/em\u003e, and your explicitly reviewed \u003cstrong\u003efailed-request count\u003c\/strong\u003e (the workflow must stop if crawl failures are indicated).\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eConfirms the Apify run is ready\u003c\/strong\u003e by calling the Apify API to ensure the specified actor run finished successfully and has a dataset available to audit.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eRuns an Apify Crawl Quality Gate\u003c\/strong\u003e actor using the dataset ID and your URL expectations, then waits briefly for completion.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eFetches and verifies the audit report\u003c\/strong\u003e from the Apify key-value store, validating it matches the expected schema and corresponds to the source run.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eRoutes the result\u003c\/strong\u003e: connect your KB refresh to \u003cstrong\u003ePASS\u003c\/strong\u003e; keep the existing KB on \u003cstrong\u003eBLOCK\u003c\/strong\u003e.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003ePrevent chatbot knowledge base refreshes when an \u003cstrong\u003eApify crawl\u003c\/strong\u003e missed required pages or produced crawl failures.\u003c\/li\u003e\n  \u003cli\u003eProtect SaaS support bots from ingesting incomplete exports during scheduled content updates.\u003c\/li\u003e\n  \u003cli\u003eAdd an approval-style gate before running your downstream n8n “KB refresh” workflow steps.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003en8n nodes\u003c\/strong\u003e: Manual Trigger, IF, Code, NoOp, HTTP Request, Sticky Note.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eApify integration\u003c\/strong\u003e: Uses an Apify API token provided as an HTTP Header Auth credential (\u003cstrong\u003eAuthorization: Bearer \u0026lt;token\u0026gt;\u003c\/strong\u003e) for all Apify HTTP requests.\u003c\/li\u003e\n  \u003cli\u003eWorkflow logic includes schema\/report matching and explicit routing to \u003cstrong\u003ePASS\u003c\/strong\u003e vs \u003cstrong\u003eBLOCK\u003c\/strong\u003e.\u003c\/li\u003e\n\u003c\/ul\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":46160846127283,"sku":"N8N-20417","price":14.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/kOtLC3x8aASrlpIlmJhjp_78Tab0bG.png?v=1791191191","url":"https:\/\/buyflowscripts.com\/products\/apify-crawl-quality-check-before-n8n-chatbot-kb-refresh","provider":"N8N Commerce","version":"1.0","type":"link"}