Government Contracts Multi-Source Monitor avatar

Government Contracts Multi-Source Monitor

Pricing

Pay per event

Go to Apify Store
Government Contracts Multi-Source Monitor

Government Contracts Multi-Source Monitor

Monitor SAM.gov, UK Contracts Finder, and EU TED contract opportunities in one normalized procurement dataset for B2G sales and proposal teams.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

19 hours ago

Last modified

Categories

Share

Track public-sector contract opportunities across SAM.gov, UK Contracts Finder, and EU TED in one normalized Apify dataset.

What does Government Contracts Multi-Source Monitor do?

Government Contracts Multi-Source Monitor searches multiple public procurement sources and returns a single feed of contract and tender opportunities.

It currently supports:

  • πŸ‡ΊπŸ‡Έ SAM.gov opportunity search
  • πŸ‡¬πŸ‡§ UK Contracts Finder OCDS releases
  • πŸ‡ͺπŸ‡Ί EU TED notices API

Each source has different fields and terminology. This actor normalizes the important procurement fields so you can compare opportunities without building three separate ingestion pipelines.

Who is it for?

This actor is useful for:

  • B2G sales teams watching new bids
  • Government contractors tracking RFPs
  • Proposal writers building a pursuit list
  • Market intelligence teams monitoring agencies
  • Consultants tracking procurement trends
  • Data teams creating a tender warehouse
  • SaaS vendors watching software and IT services tenders

Why use this actor?

Use this actor when you need one repeatable procurement monitor instead of manually checking several government portals.

Benefits:

  • One dataset across three jurisdictions
  • Source provenance on every row
  • Normalized notice IDs and buyer fields
  • Publication and deadline dates
  • CPV and NAICS category fields
  • Optional raw source JSON for audit trails
  • Built for scheduled daily or weekly monitoring

Data sources

The MVP focuses on open and recent tender/opportunity feeds:

SourceCoverageBest for
SAM.govUS federal opportunitiesUS RFPs, solicitations, awards, set-asides
UK Contracts FinderUK public procurement noticesUK tenders, awards, buyer contacts, documents
EU TEDEuropean tender noticesEU procurement by country, CPV, buyer, value

What data can you extract?

Each dataset item can include:

FieldDescription
sourceSource adapter ID
sourceNoticeIdSource notice identifier
titleOpportunity title
descriptionDescription where returned by the source
noticeTypeSolicitation, tender, award, planning, etc.
buyerNamePublic buyer or department
buyerCountryCountry code or country label
agencyAgency / authority name
publishedAtPublication date
deadlineAtResponse or tender deadline
contractValueEstimated or tender value where available
currencyValue currency
cpvCodesEU/UK CPV category codes
naicsCodesUS NAICS category codes
setAsideSAM.gov set-aside information when present
locationPlace of performance or delivery location
contactNamePublic contact name where available
contactEmailPublic contact email where available
attachmentsDocuments, PDFs, XML links, or notice documents
sourceUrlHuman-readable source page
rawOptional original source record

How much does it cost to monitor government contracts?

This actor uses pay-per-event pricing.

  • A $0.005 start event is charged once per run.
  • A result event is charged per normalized opportunity saved.
  • Formula-derived BRONZE item price: $0.000022249 per opportunity, with lower prices on higher Apify tiers.
  • You control cost with sources, maxItemsPerSource, and date filters.

For example, a daily monitor with 20 items per source across three sources will save up to 60 contract opportunities.

Quick start

  1. Open the actor on Apify.
  2. Enter one or more keywords such as software, cybersecurity, or construction.
  3. Choose sources: SAM.gov, UK Contracts Finder, EU TED, or all three.
  4. Set postedFrom for the time window you want to monitor.
  5. Set maxItemsPerSource to keep the run bounded.
  6. Run the actor.
  7. Export the dataset as JSON, CSV, Excel, RSS, or via API.

Example input

{
"keywords": ["software", "cybersecurity"],
"sources": ["sam_gov", "uk_contracts_finder", "eu_ted"],
"postedFrom": "2026-06-01",
"countries": ["USA", "GBR", "DEU"],
"cpvCodes": ["72000000"],
"naicsCodes": ["541511"],
"maxItemsPerSource": 20,
"deduplicateByUrlOrNoticeId": true,
"includeRaw": false
}

Input options

keywords

Search terms for the opportunity. Use phrases that match your target market, product, service, or procurement category.

sources

Choose one or more supported source adapters.

postedFrom and postedTo

Limit runs to a publication date window. This is ideal for scheduled monitors because each run can focus on recent notices.

deadlineFrom and deadlineTo

Deadline filters are used where source APIs support them. Some sources return deadline fields but do not expose all deadline filters.

countries

Use USA, GBR, or TED-style country codes such as DEU, FRA, or ESP.

states

Use this for US state filtering on SAM.gov where applicable.

agencies

Keep notices from buyers or agencies containing these terms.

cpvCodes

Use CPV prefixes for UK and EU procurement categories.

naicsCodes

Use NAICS prefixes for SAM.gov categories.

maxItemsPerSource

Maximum records to save from each selected source.

includeRaw

Attach the original source JSON to each row for auditing or custom mapping.

Output example

{
"source": "sam_gov",
"sourceNoticeId": "3d8a60fc686e4b5d859a83df298b0f9a",
"title": "Multiple Award Schedule",
"noticeType": "Award Notice",
"buyerName": "GENERAL SERVICES ADMINISTRATION",
"buyerCountry": "USA",
"agency": "FEDERAL ACQUISITION SERVICE",
"publishedAt": "2026-06-22T01:03:05+00:00",
"deadlineAt": "2026-06-21T16:12:13+00:00",
"cpvCodes": [],
"naicsCodes": ["513210"],
"sourceUrl": "https://sam.gov/opp/3d8a60fc686e4b5d859a83df298b0f9a/view"
}

Monitoring workflow

A common workflow is:

  • Schedule the actor daily.
  • Use postedFrom relative to your monitoring cadence.
  • Export dataset items to Google Sheets, Airtable, BigQuery, Snowflake, or your CRM.
  • Deduplicate by source + sourceNoticeId.
  • Alert proposal teams when title, description, agency, or category fields match your ICP.

Integrations

You can connect the dataset to:

  • Apify webhooks for Slack or email alerts
  • Google Sheets for pursuit pipeline review
  • Airtable for bid qualification
  • BigQuery or Snowflake for procurement intelligence
  • Zapier or Make for CRM workflows
  • Apify API for internal dashboards

API usage with Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/government-contracts-multi-source-monitor').call({
keywords: ['software'],
sources: ['sam_gov', 'uk_contracts_finder', 'eu_ted'],
maxItemsPerSource: 20,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage with Python

from apify_client import ApifyClient
client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('automation-lab/government-contracts-multi-source-monitor').call(run_input={
'keywords': ['software'],
'sources': ['sam_gov', 'uk_contracts_finder', 'eu_ted'],
'maxItemsPerSource': 20,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~government-contracts-multi-source-monitor/runs?token=MY-APIFY-TOKEN' \
-H 'Content-Type: application/json' \
-d '{"keywords":["software"],"sources":["sam_gov"],"maxItemsPerSource":20}'

MCP usage

Use this actor from Claude Desktop, Claude Code, or any MCP-compatible client through the Apify MCP server.

MCP tool URL:

https://mcp.apify.com/?tools=automation-lab/government-contracts-multi-source-monitor

Claude Code setup example:

$claude mcp add apify-government-contracts --url "https://mcp.apify.com/?tools=automation-lab/government-contracts-multi-source-monitor"

Claude Desktop JSON config example:

{
"mcpServers": {
"apify-government-contracts": {
"url": "https://mcp.apify.com/?tools=automation-lab/government-contracts-multi-source-monitor"
}
}
}

Example prompt ideas for MCP:

  • "Use the automation-lab/government-contracts-multi-source-monitor MCP tool to find new software contracts from SAM.gov and TED."
  • "Run the government contracts monitor MCP tool for UK cybersecurity tenders and summarize buyer names and deadlines."
  • "Use MCP to create a normalized CSV of EU and US contract opportunities published this week."

Tips for better results

  • Use specific service keywords instead of generic words.
  • Combine keywords with CPV or NAICS filters when possible.
  • Start with a small maxItemsPerSource while tuning filters.
  • Use includeRaw only when you need original source records.
  • Schedule runs for monitoring instead of running large historical backfills.

Common CPV examples

  • 72000000 β€” IT services
  • 48000000 β€” Software packages
  • 45000000 β€” Construction work
  • 33000000 β€” Medical equipment
  • 79000000 β€” Business services

Common NAICS examples

  • 541511 β€” Custom computer programming services
  • 541512 β€” Computer systems design services
  • 541519 β€” Other computer related services
  • 541611 β€” Administrative management consulting
  • 561210 β€” Facilities support services

Limitations

  • Source APIs can expose different fields.
  • Some sources search hidden/full-text fields that are not returned in normalized output.
  • TED localization depends on the fields returned by the TED API.
  • USAspending awards are not included in MVP because they are not open bid opportunities.
  • Rate limits on public sources can temporarily reduce one source while other sources still finish.

FAQ

Can I run this actor on a schedule?

Yes. Schedule it daily or weekly and use a recent postedFrom date so each run captures new contract opportunities.

Does this replace the single-source actors?

Use this actor for a normalized cross-source feed. Use the single-source actors when you need source-specific fields or deeper coverage for one portal.

Troubleshooting

Why are some fields empty?

Not every source publishes every field. For example, SAM.gov may not return CPV codes, while EU TED may not return NAICS codes.

Why did one source return fewer items?

The source may have fewer matching notices, a public API rate limit, or filters that are too narrow. Try reducing filters or running a single source to diagnose.

Why does the actor continue if one source fails?

For monitor reliability, a temporary failure in one public endpoint should not prevent other sources from producing usable records.

Legality

This actor collects public procurement data from public government and public-sector endpoints. You are responsible for using the data in accordance with source terms, applicable law, and your compliance requirements.

Changelog

Initial MVP includes SAM.gov, UK Contracts Finder, and EU TED source adapters with a normalized contract opportunity dataset.