Gate saved crawl batches before RAG ingestion with Apify Recency Actor
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs manually, when you click “Execute workflow”. It uses only n8n's built-in nodes. It also calls api.apify.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Simulate Ingestion Process (Code): runs custom JavaScript code
- Prepare Metadata Batch (Code): runs custom JavaScript code
- Post to Recency Actor API (HTTP Request): calls api.apify.com (POST)
- Check Gate Report (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Ingest Data (Code): runs custom JavaScript code
- Diagnose Blocked Batch (Code): runs custom JavaScript code
HTTP calls to: api.apify.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (4)
- Manual Trigger
n8n-nodes-base.manualTrigger - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if
From the author
Quick overview This workflow manually tests a saved crawl batch for recency by sending document capture metadata to an Apify Actor, then either releases the original documents for downstream ingestion or blocks the entire batch and returns diagnostics. How it…