B2B Trigger Event Radar: Funding, Hiring & Launch Signals
Pricing
from $50.00 / 1,000 account with active triggers
B2B Trigger Event Radar: Funding, Hiring & Launch Signals
Scan target accounts for live buying triggers (funding & M&A, exec hires, launches, hiring sprees, compliance/security, expansion) with a 1-10 priority score and a tactful why-now hook. Quiet accounts are free.
Pricing
from $50.00 / 1,000 account with active triggers
Rating
0.0
(0)
Developer
Jonny Dean
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Scans your target accounts for live buying signals (funding and M&A, exec hires, product launches, hiring sprees, compliance/security events, expansion) and returns a dated trigger, a 1–10 priority score, and a tactful "why reach out now" hook. Quiet accounts are free.
Built for SDRs, AEs, ABM/RevOps teams, agencies, and Clay users who want sales intelligence on which accounts to work this week.
Who it's for
- Clay users who want a cheap, live trigger column next to their enrichment waterfall (call it through Clay's HTTP API / Apify integration)
- SDRs and AEs prioritizing named accounts each week
- ABM and RevOps teams who need signal-based account scoring
- Agencies running signal-based outbound for clients
What you get for each company
| Field | What it is |
|---|---|
company_name, domain | The account that was scanned |
active_trigger_detected | true if a qualifying, verifiable event was found |
primary_trigger_category | funding_mna, exec_hire, product_launch, hiring_spree, regulatory_or_security, expansion, or none |
trigger_summary_with_date | What happened and roughly when |
trigger_date, trigger_source_url | Date of the event and a source link |
account_priority_score | 1–10: how strongly the trigger suggests reaching out now for your offer |
why_reach_out_now_hook | A one-sentence opener. It stays tactful and never gloats about breaches or layoffs. |
charged | false for quiet accounts (no charge) |
cached_result | true if served from the 24-hour cache |
How to use it
- Add companies as
{"company": "...", "domain": "..."}. The domain is optional but improves accuracy. - Pick the trigger types you care about (all are selected by default).
- Describe your offer so the score and hook match your pitch.
- Sort by
account_priority_scoreand work the top of the list.
Example input
{"companies": [{ "company": "Ramp", "domain": "ramp.com" },{ "company": "Vanta", "domain": "vanta.com" }],"target_trigger_types": ["funding_mna", "exec_hire", "product_launch", "hiring_spree"],"sender_offer_context": "Outsourced RevOps and CRM automation for fast-growing B2B teams","use_cache": true}
Example output
Real results from test runs on Oct 21–22, 2026 (offer: outsourced RevOps and CRM automation), shortened for display:
| Company | Trigger | What happened | Priority | Charged |
|---|---|---|---|---|
| Ramp | funding_mna | Raised $1.85B at a $60B valuation, Oct 15, 2026 (TechCrunch) | 9 | yes |
| Notion | product_launch | Major Notion AI upgrades: rebuilt Agents with computer/browser use, BYOK, new credit system, Oct 19, 2026 (release notes) | 8 | yes |
| Vercel | product_launch | Ship 2026 announcements incl. Python on Vercel GA and Vercel Drives, Oct 15, 2026 (blog) | 8 | yes |
| A small regional supplier | none | No active trigger found | 2 | no |
Example hook (Ramp): "With Ramp's accelerated growth following its recent funding round, supporting efficient RevOps and CRM scaling could help maximize their momentum."
Pricing
Pay-per-event: $0.05 per company with an active trigger (event account-scored, $50 per 1,000 triggered accounts), plus a negligible Apify start fee. No charge when nothing real is found: quiet companies (primary_trigger_category: none) and failed lookups are returned free. Use maximum cost per run to cap spend.
Free Apify plan users can scan up to 3 companies per run.
Using it from Clay
Add an HTTP API enrichment (or the Apify integration) that calls this Actor's run-sync-get-dataset-items endpoint with {"companies":[{"company":"{{Company}}","domain":"{{Domain}}"}]}. Then map primary_trigger_category, account_priority_score, and why_reach_out_now_hook into columns. Since quiet rows are free, you can run it across your whole TAM.
Pairs well with
- Live X & Web B2B Lead Enricher + Cold Email Icebreaker: once you know which accounts to work, enrich the people there with a personalized, recent-activity icebreaker ($0.10 per enriched lead).
- Journalist, Podcast & Creator Pitch Dossier Generator: research what a journalist, podcaster or creator covered recently and get a tailored pitch subject line and hook ($0.10 per dossier).
Integrations
- Apify API: start runs and fetch results with the REST API or the
run-sync-get-dataset-itemsendpoint (JavaScript and Python clients available). - Zapier, Make, and n8n: use the official Apify apps/nodes to run this Actor from a workflow and push results to your CRM, sheet, or email tool.
- Webhooks: get notified when a run finishes and pull the dataset automatically.
- AI agents: AI assistants and agents can call this Actor as a tool through the Apify MCP server.
- Exports: download results as JSON, CSV, Excel, or HTML from the Console.
Tips for better results
- Always pass the domain. It removes ambiguity between companies with similar names.
- Narrow the trigger types to the ones that predict your deals.
- Re-run weekly. The 24-hour cache prevents double billing within a day.
- Security or regulatory triggers are reported so you have the context, but the hook deliberately avoids mentioning them. Check the summary before referencing anything sensitive.
FAQ
Where does the data come from? Public news, press releases, company sites, job boards, and X posts, researched live at run time.
How recent are triggers? It looks back 90 days and prefers the last 30, with each trigger dated.
Will it make things up? It's instructed to report only events it actually found. With no evidence, the account is marked none and not charged.
Is it compliant? It only uses publicly available information. You're responsible for following anti-spam laws (CAN-SPAM, GDPR, etc.) in your outreach.
Support
Found a bug or want a feature? Open an issue on the Actor's Issues tab and I'll respond quickly.