Public procurement / tender monitor

Monitor procurement, tender, and RFP pages for fresh opportunities that match your keyword list. This Actor is designed for buyers who want a simple, recurring way to discover commercial opportunities without manually checking dozens of government and procurement pages.

What does this Actor do?

• Fetches one or more procurement or tender sources.
• Extracts matching records from HTML or JSON pages.
• Saves each match to the dataset.
• Writes the full result bundle to the OUTPUT key-value record.

The Actor is meant to be sold as a practical B2B monitoring tool: buyers supply their own sources, keywords, and lookback window, then run it on a schedule or via API.

Why use it?

• Save time versus manual procurement checks.
• Catch new opportunities faster.
• Reuse the same Actor across countries, industries, and source lists.
• Integrate with Apify scheduling, webhooks, and downstream automation.

How to use it

1. Open the Actor on Apify.
2. Add one or more source_urls.
3. Set your keywords.
4. Choose lookback_days and max_items.
5. Run it once to confirm the sources work.
6. Put it on a schedule if you want recurring monitoring.

Input

Main inputs:

• source_urls — procurement pages, search result pages, RSS feeds, or JSON endpoints.
• country — reporting hint.
• language — reporting hint.
• lookback_days — how far back to consider results.
• keywords — words or phrases that mark a relevant opportunity.
• max_items — maximum results per run.

Suggested starting values are already prefilled in the schema.

Output

The Actor returns:

• items[] with title, url, source, source_url, published_at, snippet, and matched_keyword
• summary with counts and runtime
• warnings[] for fetch or parsing issues

Example output:

{
  "items": [
    {
      "title": "Tender for office supplies",
      "url": "https://example.com/tender/123",
      "source": "example.com",
      "source_url": "https://example.com/search",
      "published_at": "2026-07-01T10:00:00Z",
      "snippet": "... procurement ...",
      "matched_keyword": "procurement"
    }
  ],
  "summary": {
    "count": 1,
    "source_count": 1,
    "keyword_count": 5,
    "lookback_days": 30,
    "country": "UK",
    "language": "en",
    "run_time_ms": 1234,
    "warnings_count": 0
  },
  "warnings": []
}

You can download the dataset in JSON, CSV, Excel, HTML, RSS, and other standard Apify formats.

Data table

The main dataset fields are:

• title
• url
• source
• source_url
• published_at
• snippet
• matched_keyword

Pricing / cost estimation

This Actor is intended for pay-per-event monetization.

Recommended setup:

• charge per dataset item processed
• keep the first-run max cost low
• expose a clear max charge per run so customers can control spend

For buyers, the cost stays predictable because the main event is tied to output volume.

Tips

• Start with a small list of source URLs.
• Use narrow keywords first, then broaden them.
• Prefer stable HTML or JSON endpoints over highly dynamic pages.
• Keep the run schedule aligned with how often the target sources update.

FAQ / support

Does it work on every site? No. Some sources need selector tuning or proxy support.

Is it legal to scrape procurement pages? Use it only where you have the right to access and process the data, and follow each site’s terms.

Need a custom version? This Actor is designed to be adapted for a specific source or market.

Deploy

From this directory:

npx -y apify-cli login --token "$APIFY_TOKEN"
npx -y apify-cli actors push --dir . --json --wait-for-finish 0

Managed by Hermes

The portfolio automation is designed to:

• deploy this Actor when the scanner selects it
• retire it if monthly review flags it as unprofitable
• keep future Actors public-ready and sales-oriented