New Zealand GETS Tender Feed

The GETS Tender Feed actor scrapes the public New Zealand Government Electronic Tenders Service index to generate a filtered feed of live RFx opportunities—no RealMe login required.

🚀 Functional Overview

This actor downloads the public tender table, parses every row with CheerioCrawler, and outputs normalized JSON containing RFx ID, titles, tender types, agencies, and close dates in ISO 8601.

💡 Key Features

• No login / no CAPTCHA: Pulls straight from the public metadata page.
• Category + keyword filters: Focus on UNSPSC codes or industry phrases.
• Tender-type controls: Only watch ROIs, RFQs, or RFTs that matter.
• Clean ISO timestamps: Close dates converted to UTC for downstream automation.
• Low CU footprint: Single HTTP request + HTML parse keeps costs near zero.

🎯 Who Is It For?

• SME biz-dev teams that need daily procurement alerts without logging into GETS.
• GovTech and compliance SaaS platforms building automated tender monitors.
• Consultants/analysts tracking signal volume for specific agencies or UNSPSC codes.

📊 Data Extracted

Field	Description
id	Official RFx identifier shown in the GETS table.
reference	Secondary reference / agency code when provided.
title	Tender title.
tender_type	RFx type (NOI, ROI, RFP, RFQ, RFT).
organisation	Publishing agency or council.
close_date	ISO timestamp (Pacific/Auckland → UTC).
close_date_raw	Original close date text for auditing.
detail_url	Direct link to the GETS detail page.
source_url	Listing page used for the run.
categoryMatches	Array of matched category codes (optional).
extracted_at	ISO timestamp when the record was scraped.

⚡ Quick Start Guide

1. Open the actor on Apify Store and click Try for free.
2. Leave the default startUrls (or add filtered/sorted GETS list URLs).
3. Enter UNSPSC or agency codes in categoryCodes to pre-filter.
4. Add include/exclude keywords to tighten the feed; pick tender types (ROI/RFP/RFT/etc.).
5. Set maxItems (e.g., 100). Click Run.
6. When the run finishes, download the Dataset as JSON/CSV or access via API/webhooks.

📥 Input Parameters

Name	Type	Required	Default	Description
startUrls	Array	✅	ExternalIndex.htm	GETS listing URLs to crawl. Accepts sorted versions (orderBy=ref, etc.).
categoryCodes	Array	❌	[]	Optional UNSPSC/agency codes to match against title/reference text.
keywordIncludes	Array	❌	[]	Only emit tenders that contain at least one keyword (case-insensitive).
keywordExcludes	Array	❌	[]	Drop tenders containing any of these keywords.
tenderTypes	Array	❌	[]	Limit to specific RFx types (NOI, RFQ, RFP, ROI, RFT).
maxItems	Integer	❌	200	Hard cap on number of records pushed per run.
proxyConfiguration	Object	❌	Apify datacenter	Use default Apify proxy. Residential pools rarely required.

📤 Output Schema

{
  "id": "33592807",
  "reference": "NZBS-2026-P2P",
  "title": "Procure to Pay Platform (P2P)",
  "tender_type": "ROI",
  "organisation": "New Zealand Blood Service",
  "close_date": "2026-03-04T23:00:00.000Z",
  "close_date_raw": "12:00 PM 5 Mar 2026 (Pacific/Auckland UTC+13:00)",
  "detail_url": "https://www.gets.govt.nz/NZBS/ExternalTenderDetails.htm?id=33498430",
  "source_url": "https://www.gets.govt.nz/ExternalIndex.htm",
  "categoryMatches": ["93131700"],
  "extracted_at": "2026-03-04T08:15:33.102Z"
}

💰 Pricing & Compute Units

• Estimated CU: ~0.02 CU per 500 tenders (one HTML request + Cheerio parse).
• Scaling tip: Increase maxItems gradually; CU usage scales linearly with rows processed.
• Proxy cost: Default Apify datacenter proxy is sufficient; residential proxies optional.

🛠️ FAQ & Troubleshooting

Do I need a RealMe login? No. The actor uses only the public tender index.

The run returned zero items. Why? Most likely filters were too strict. Remove categoryCodes/keywords to confirm data is flowing, then reintroduce them.

Can I fetch full tender documents? No, RealMe authentication is required for downloads. This actor is best for discovery feeds and alerting.

How do I get notified on new tenders? Use Apify webhooks (ACTOR.RUN.SUCCEEDED) or schedule the actor hourly and connect the dataset to Make/Zapier.

🔌 Integrations

• Apify API: Access datasets via https://api.apify.com/v2/datasets/<datasetId>/items.
• Make / Zapier: Consume dataset webhooks to populate Slack, email digests, or CRMs.
• Google Sheets: Use Apify’s Google Sheets integration to auto-sync the dataset.

📈 Maintenance & Quality

• Built with CheerioCrawler for deterministic output (no browser flakiness).
• Limited permissions by default—only accesses its own storages.
• Designed per Apify Playbook best practices with logging + schema validation hooks.

Need additional fields (e.g., auto-follow detail pages)? Open an issue on the Actor page and we can extend the extractor.