Pricing

Rating

Developer

Actor stats

Categories

Share

🎯 GTM Trigger Feed — Funding, Licenses, Layoffs & Openings

One unified buying-intent signal feed, built entirely from public records. Instead of running five separate monitors, this actor aggregates the strongest GTM trigger events — new SEC Form D funding rounds, 8-K executive changes, WARN mass-layoff notices, new city business licenses, new liquor licenses, and new ATS job postings — into a single normalized feed. Run it on a schedule in monitor mode and get ONLY the new signals, alerted to Slack, email, or any webhook.

No login or API key — every source is a public government record or a public job-board API. A pay-per-event alternative to PredictLeads and Mantiks.

Why trigger events win deals

A static lead list goes stale; a trigger event tells you who is buying right now:

• 💰 Funding (SEC Form D) — "just raised money" = new budget to spend. Includes the $ amount and named principals.
• 👔 Exec change (SEC 8-K Item 5.02) — a new officer/director = new initiatives and re-opened vendor decisions.
• 📉 Layoffs (WARN Act notices) — talent hitting the market (recruiters), a competitor in distress (sales/M&A), an active outplacement buyer.
• 🏪 New business licenses (city registries) — a business opening or expanding = merchant services, insurance, suppliers, CRE.
• 🍸 New liquor licenses (state ABC boards) — a bar/restaurant opening months before it's on Google Maps.
• 🧑‍💻 New job postings (company ATS boards) — hiring for X = investing in X; a wave of AE reqs = scaling GTM.

Every record comes out in one shape, so the whole feed drops straight into Clay, your CRM, or n8n:

{
"signal_type":"funding",
"company_or_name":"Acme Robotics, Inc.",
"location":"Austin",
"state":"TX",
"date":"2026-06-10",
"details":"Form D private raise — raised $12,500,000 · Other Technology · Jane Doe (Executive Officer)",
"source":"SEC EDGAR Form D",
"url":"https://www.sec.gov/Archives/edgar/data/…-index.htm",
"record_id":"fund:0001234567-26-000123",
"is_new":true,
"scraped_at":"2026-06-12T15:04:05.000Z"
}

Signals & sources (all public, validated live)

⚠️ jobs requires your target list. There is no global job feed — you must supply atsTargets (board URLs or ats:token, e.g. greenhouse:stripe). That's why jobs is OFF in the default input. All other signals work with zero configuration.

Input

Quick start (the default — runs in seconds)

{"signalTypes":["warn_layoff","business_license"],"lookbackDays":7,"maxRecords":250}

The full feed

{
"signalTypes":["warn_layoff","business_license","liquor_license","funding","exec_change","jobs"],
"atsTargets":["greenhouse:stripe","lever:shopify"],
"states":[],
"lookbackDays":7,
"contactEmail":"you@company.com"
}

Daily monitor → Slack

{
"signalTypes":["funding","exec_change","warn_layoff"],
"lookbackDays":7,
"monitorMode":true,
"alertOnNewSignal":true,
"slackWebhookUrl":"https://hooks.slack.com/services/…"
}

Turn on Monitor mode, add an Apify Schedule (e.g. daily), and each run emits only the signals it hasn't seen before — no double-counting, ever (state lives in a named key-value store that persists across runs).

Output

One dataset item per signal:

signal_type · company_or_name · location · state · date (YYYY-MM-DD) · details · source · url · record_id · is_new (monitor mode) · scraped_at

Export to JSON, CSV, Excel, HTML, or RSS — or pull via the Apify API into Clay, your CRM, n8n, or a spreadsheet.

Pricing (pay-per-event)

A typical daily monitor (one run, a handful of new signals + alerts) costs a few cents — versus hundreds of dollars per month for SaaS trigger-data platforms like PredictLeads or Mantiks.

FAQ

Do I need any account, login, or API key? No. Every source is a public record or a public no-auth API. An optional free Socrata app token raises rate limits, and an optional contact email is added to SEC requests (their courtesy convention).

Why are only two signals on by default? They're the fastest, most reliable feeds (pure JSON, seconds per run). Turn on the rest in signalTypes — funding/exec_change add SEC fetches, liquor_license adds CA's per-day HTML reports, and jobs needs your atsTargets.

How do I get only NEW signals? Set monitorMode: true and run on a Schedule. The actor remembers what it has seen (per signal+state+keyword scope) and emits each signal once.

What if one source is down? Per-source failures are logged and skipped — the rest of the feed still delivers. A run never fails because one agency's site hiccuped.

Can I filter to my territory? Yes — states filters WARN/licenses and SEC filings by filer state; keyword filters everything by company/details/location text.

What's in details? A human-readable one-liner per signal: employees affected + effective date (layoffs), license type (licenses), $ raised + industry + principals (funding), the job title (jobs).

Where does the SEC data come from? The EDGAR full-text-search API (Form D and 8-K). Form D filings are enriched from the filing's primary_doc.xml. SEC is always fetched direct (no proxy) per their access guidance.

Is this legal to use? All sources are public government records or public job-board APIs intended for consumption. Review each agency's/platform's terms; how you use the data is your call.

Can you add more states/cities? Yes — the per-source adapters drop in cleanly (CA/OH/NY WARN, more cities, more ATS). Ask via an issue.

How is this different from running the five individual monitors? One run, one schedule, one dataset, one webhook — and every record in the same shape, so your downstream table/Clay workflow needs exactly one column mapping.

Notes

• Public records (business/employer-level; Form D principals are a public federal disclosure) — surface only what the source publishes; your use is your call.
• No double-counting — monitor state lives in the named gtm-trigger-feed-state store and persists across runs.
• Coverage grows — adapters are per-source; new states/cities/ATS land without breaking your runs.