Monitor EU TED tenders with Apify and store notices in n8n Data Tables
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Apify (community).
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Set Actor Task ID (Edit Fields (Set)): sets 1 field: actorTaskId
- Execute TED Monitoring Task (Apify): run task (actor tasks)
- Check Dataset Availability (If): checks a condition and branches into true / false
- Fetch Dataset Records (Apify): get items (datasets)
- Report No Dataset Found (Code): runs custom JavaScript code
- Process Dataset Records (Code): runs custom JavaScript code
- Check for Record Presence (If): checks a condition and branches into true / false
- Upsert TED Records (Data table): create or update (row)
- Report After Ingestion (Code): runs custom JavaScript code
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @apify/n8n-nodes-apify is verified or supports 3.0 (used in Execute TED Monitoring Task, Fetch Dataset Records).
Nodes used (7)
- Manual Trigger
n8n-nodes-base.manualTrigger - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Apify
@apify/n8n-nodes-apify.apify - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Data table
n8n-nodes-base.dataTable
From the author
Quick overview This workflow runs daily (or manually) to execute an Apify TED monitoring Task, fetch its results dataset, normalize each EU tender notice record, and upsert the records into an n8n Data Table for deduplicated storage and reporting. How it…