Tender Signal Harvester

Extract tender, RFP, solicitation, deadline, buyer, budget, category, and qualification signals from public procurement pages or pasted notices.

Tender Signal Harvester is for teams that need to qualify public-sector and enterprise procurement opportunities quickly. Instead of saving a generic page summary, it turns each public notice into a row that highlights the buyer, deadline, contract value, supplier requirements, and the next action a sales or bids team should review.

This actor is designed for focused marketplace research runs. You can give it public URLs, paste copied source text, or combine both. URL fetching is useful for public HTML pages; pasted text is useful when a site uses heavy JavaScript, login walls, CAPTCHA, or restrictive anti-bot controls that should not be bypassed.

Who Uses It

• Bid teams and proposal writers
• B2B sales teams watching public procurement
• Agencies finding implementation opportunities
• Market researchers tracking funded projects
• Vendors monitoring RFP deadlines

What It Extracts

• opportunityTitle - Tender, RFP, RFQ, solicitation, or procurement opportunity title.
• buyerName - Public buyer, agency, city, ministry, university, or department issuing the opportunity.
• tenderType - Tender format such as RFP, RFQ, bid, solicitation, grant, award, or contract notice.
• deadline - Submission, closing, due, or questions deadline found in the source.
• budgetOrValue - Visible budget, contract value, award value, or spend estimate.
• procurementStage - Buyer-stage signal such as open tender, questions due, site visit, award expected, or closed notice.
• category - Likely procurement category such as IT services, healthcare, construction, facilities, security, or professional services.
• eligibilitySignal - Supplier qualification, preference, region, certification, or eligibility rule.
• contactEmail - Procurement or buyer contact email when visible.
• sourceUrl - Original URL or synthetic URL for pasted notice text.
• leadPriority - Priority based on deadline, value, stage, and fit indicators.
• evidenceText - Short source sentence supporting the extracted opportunity.

Why This Actor Is Useful

Tender pages are often long, inconsistent, and full of administrative wording. This actor highlights the parts a commercial team needs first: buyer, due date, budget, qualification rules, category, and evidence.

Input

• startUrls - Public pages to fetch and analyze.
• sourceTexts - Optional pasted source snippets for pages that are blocked, login-gated, JavaScript-heavy, or easier to collect manually.
• maxPagesPerStartUrl - Same-domain crawl depth for each URL. Use a low value for precise runs.
• maxConcurrency - Parallel request count.
• proxyConfiguration - Optional Apify Proxy settings for public pages that rate-limit normal requests.

Example Input

{
    "startUrls": [
        {
            "url": "https://sam.gov/search/"
        }
    ],
    "sourceTexts": [
        "City of Lakes Procurement Office RFP 24-118 seeks a cloud document management vendor. Submission deadline August 30, 2026. Estimated contract value $250,000. Questions due August 12. Open competitive solicitation for municipal IT services in Minnesota. Contact procurement@cityoflakes.gov."
    ],
    "maxPagesPerStartUrl": 2,
    "maxConcurrency": 2
}

Example Output

{
    "opportunityTitle": "RFP 24-118 cloud document management vendor",
    "buyerName": "City of Lakes Procurement Office",
    "tenderType": "RFP",
    "deadline": "August 30, 2026",
    "budgetOrValue": "$250,000",
    "procurementStage": "open competitive solicitation",
    "category": "IT services",
    "eligibilitySignal": "Questions due August 12",
    "contactEmail": "procurement@cityoflakes.gov",
    "sourceUrl": "pasted://tender-1",
    "leadPriority": "high",
    "evidenceText": "Submission deadline August 30, 2026. Estimated contract value $250,000."
}

How It Works

1. The actor normalizes every URL and pasted text item.
2. Public URLs are fetched with a browser-like user agent and a clear timeout.
3. HTML pages are converted into readable page text while scripts, styles, iframes, and hidden noise are removed.
4. The actor applies Tender Signal Harvester-specific extraction rules rather than a generic page-summary template.
5. Only rows with useful actor-specific information are saved to the dataset.
6. A run summary is saved to the key-value store for quick review.

Practical Workflows

• Build a daily spreadsheet of qualified RFPs.
• Route high-value tenders to proposal owners.
• Watch public procurement portals for deadlines and qualification rules.
• Enrich CRM accounts with active buying signals.

Reliability Notes

• Best results come from public HTML pages or pasted snippets that visibly contain the target signal.
• For JavaScript-heavy sites, paste the relevant text or use URLs that return readable HTML.
• The actor does not bypass logins, paywalls, CAPTCHA, private systems, or website restrictions.
• Some fields may be empty when the source does not contain that information.
• Use smaller crawl limits for broad portals and larger limits only for well-structured sites.

Limitations

• This actor extracts public or user-provided visible text only.
• It is not a legal-access tool for restricted procurement portals, private retailer dashboards, closed review platforms, account-only changelogs, or internal documentation.
• Results should be reviewed before making procurement, legal, inventory, engineering, or sales decisions.

Search Keywords

tender signal harvester, tender signal harvester, opportunity title, buyer name, tender type, deadline, budget or value, procurement stage, category, eligibility signal, contact email, source url, lead priority, evidence text