Apify TED Monitor to n8n Data Tables EU Tender Notices

Apify TED monitoring results automatically land in n8n Data Tables (deduplicated) for EU tender notices

This n8n automation runs an Apify “TED Monitor” task, normalizes each EU tender notice record, and upserts it into an n8n Data Table using a stable delivery key—so you get clean, deduplicated data for reporting and tracking.

What this workflow does

• Runs daily at 06:00 (or can be started manually for testing).
• Executes an Apify Actor Task for TED monitoring and waits for the run to finish.
• If the Apify run provides a default dataset, retrieves up to 1,000 dataset items.
• Cleans and normalizes each dataset row into a consistent structure.
• Generates a stable delivery key (for example, based on the TED publication number) and keeps the full raw payload as JSON.
• Upserts records into an n8n Data Table (deduplication) using the delivery key as the unique match column.
• Outputs a run summary (including tender counts) and fails the workflow if the Apify run did not succeed or no dataset was available.

Use cases

• Maintain an always-current internal database of EU tender notices for compliance or sourcing workflows.
• Feed dashboards and reporting layers with consistent, deduplicated tender data.
• Test and validate Apify TED monitoring filters (e.g., CPV, country, keywords, notice type) before scaling operations.

Technical details

• Apify integration: Uses the community node package @apify/n8n-nodes-apify (version 0.6.10+).
• Nodes used: if, set, code, Data Table, and an Apify node (@apify/n8n-nodes-apify).
• Data storage: Upserts into an n8n Data Table named monitor-deliveries with a unique deliveryKey.

Set your Apify token credential, provide the TED monitoring Actor Task ID, configure saved Task inputs/filters, and keep maxNewPerRun at 999 or less for reliable non-paginated fetching.