Hyreflow
Integrations

LayoffSignal

Layoff/RIF signal tracker over free public RSS — surfaces recent layoff news as a poach trigger. Key gotcha: results are redirect links only; resolve them with Firecrawl.

Reach for LayoffSignal when the trigger is "company is cutting staff": sweep the last 7 days of tech layoffs or scope a named employer, then poach displaced talent and open BD with the survivors. A Hyreflow Native built on free public RSS — no API key.

Native (free, no BYOK) — first-party capability on free public RSS; 0 credits under current pricing, and the provider-precedence waterfall does not apply.

Capabilities

ToolDoesCost
layoff_newsPre-built layoff-terms Google News query; pass company to scope, when for recencyFree
google_newsRaw Google News RSS search with full operators (site:, OR, intitle:, -)Free
iter_layoff_newsWhole-stream sweep: broad query + per-company + site feedsFree
site_feed / site_feedsFetch publisher RSS/Atom feeds → clean direct linksFree
resolve_linkBest-effort follow a redirector → publisher URLFree

Guidance

  • Discovery returns links only — fetch article bodies separately. google_news/layoff_news links are Google News redirectors, so hand them to Firecrawl (it follows the redirect and returns the body) or try resolve_link.
  • Prefer per-site feeds for clean links: site_feed() gives direct publisher URLs with no redirector to resolve. Paywalled outlets (Bloomberg/Reuters) only surface via google_news.
  • Use when= for recency (7d/24h/1h); layoff_news OR-joins layoff terms automatically.
  • Use it as a signal/trigger, not a redistributed dataset — attribute the originating publisher; don't resell curated databases.
  • Recipe: sweep → resolve+fetch bodies (Firecrawl) → Claude extracts {company, headcount, %, date, location, source} → dedupe → source affected roles → enrich → outreach/ATS.
hyreflow tools execute layoffsignal layoff_news \
  --payload '{"company":"Microsoft","when":"30d"}'

Every op is free (0 credits) under current pricing — the feed pull itself costs nothing, so it's safe to sweep broadly, then narrow with company.

On this page