Apify Crawl Quality Check Before n8n Chatbot KB Refresh

Before you refresh your n8n Chatbot knowledge base, confirm your Apify crawl is actually usable.

This Apify Crawl Quality Check Before n8n Chatbot KB Refresh 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 PASS (you refresh the KB) or BLOCK (you keep the current knowledge base) without writing to your destination.

What this workflow does

• Manual trigger in n8n to start the quality gate when you’re ready to refresh.
• Validates required configuration: reads your configured Apify crawl run ID, namespace, expected URLs, and your explicitly reviewed failed-request count (the workflow must stop if crawl failures are indicated).
• Confirms the Apify run is ready by calling the Apify API to ensure the specified actor run finished successfully and has a dataset available to audit.
• Runs an Apify Crawl Quality Gate actor using the dataset ID and your URL expectations, then waits briefly for completion.
• Fetches and verifies the audit report from the Apify key-value store, validating it matches the expected schema and corresponds to the source run.
• Routes the result: connect your KB refresh to PASS; keep the existing KB on BLOCK.

Use cases

• Prevent chatbot knowledge base refreshes when an Apify crawl missed required pages or produced crawl failures.
• Protect SaaS support bots from ingesting incomplete exports during scheduled content updates.
• Add an approval-style gate before running your downstream n8n “KB refresh” workflow steps.

Technical details

• n8n nodes: Manual Trigger, IF, Code, NoOp, HTTP Request, Sticky Note.
• Apify integration: Uses an Apify API token provided as an HTTP Header Auth credential (Authorization: Bearer <token>) for all Apify HTTP requests.
• Workflow logic includes schema/report matching and explicit routing to PASS vs BLOCK.