EU Tender Monitor (TED)
Pricing
Pay per usage
Monitor and track EU tender notices from TED (Tenders Electronic Daily). Supports filtering, change detection, and automation-ready output.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
certex
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Buyer country codes for discovery mode. Use codes such as POL, DEU, or FRA. Use countries when you want to search TED, not when you want persisted monitoring and diffing.
[ "POL"][ "DEU"]Exact TED publication numbers to track directly, for example 136392-2025. Use this mode to monitor a fixed shortlist of up to 50 notices without search-window churn.
[ "136392-2025", "140001-2025"]Optional shortcut that adds common CPV codes and search terms for a topic.
Optional exact 8-digit CPV codes. These are merged with preset values when a preset is used.
[ "72000000", "48814000"]Optional terms sent to TED and matched against TED notice titles. These are merged with preset search terms when a preset is used.
[ "hospital software"]Optional keywords used after fetch to intelligently rank tenders across EU languages and wording differences. Keyword phrases usually give the best results, for example school management system or student information system. Use keywords to improve result quality and reduce missed opportunities.
[ "school management system", "student information system", "digital learning"]Optional manual tagging rules. Each rule should contain a tag and a matchAny list of text or CPV terms.
[ { "tag": "strategic-account", "matchAny": [ "hospital", "48814000" ] }]Optional text filter for buyer names, such as city hospital or ministry.
Optional shortcut for recent monitoring. If explicit publishedFrom or publishedTo is set, those dates take precedence over daysBack.
Optional lower bound for publication date in ISO-like format.
Optional upper bound for publication date in ISO-like format.
Maximum number of TED notices fetched in one run. Supports bulk runs up to 15000 notices in discovery mode. When keywords are used, maxResults must not exceed 1000 so keyword ranking stays predictable.
If true, compare the current run to the previous snapshot and produce change events. Diffing is supported only with noticeIds exact tracking.
If true, return only new or changed tenders from the tracked noticeIds list. Requires noticeIds and a unique trackingName for that monitoring stream.
If true, generate Telegram-friendly summary and item payloads in Actor output.
If true and both telegramBotToken and telegramChatId are provided, the Actor sends Telegram messages after the run finishes.
Telegram Bot API token used for direct message delivery.
Target Telegram chat ID for direct alert delivery.
Choose whether to send only the summary, only item messages, or both.
If true, Telegram link previews are disabled in direct messages.
If true, the Actor run fails when direct Telegram delivery fails.
If true, generate compact webhook-friendly payloads for external automation tools.
Optional direct webhook endpoint for Zapier, Make, n8n, Slack-compatible webhooks, or custom HTTP receivers.
If true and webhookUrl is provided, the Actor posts webhook payloads directly after the run finishes.
Optional shared secret sent in the X-Webhook-Secret header.
Optional custom HTTP headers to include in the outbound webhook request.
{ "X-Environment": "production"}Choose whether to send only the summary payload, only items, or both together.
If true, the Actor run fails when direct webhook delivery fails.
If true, unchanged tenders are kept in the output even when monitoring mode is enabled.
Unique name for this monitoring stream, such as customer-a-hospital-bids-2026-q1. Required for monitoringMode. Reusing the same trackingName means reusing the same saved monitoring history across runs, and another Actor user can accidentally overwrite or mix that history if they choose the same name.