Skip to main content

​
What It Does

  • Surfaces recent news mentions for each company in your table
  • Uses the domain to find articles tied to that organization
  • Returns article-level insights like headline, link, and detection timestamp
  • Outputs one row per article — so companies with more coverage show up more
  • Automatically handles column name clashes like title or timestamp
All headlines come from Predictleads, our trusted news enrichment vendor — for now. We’re exploring more sources soon.

​
🏁 Getting Started

Get Company News node config
1

Add the Node

Drop Get Company News into your flow — it’s especially useful post-enrichment or after scoring.
2

Map the Domain

Use a static domain (nrev.ai) or reference a mapped column like @domain from earlier in your pipeline.
3

Set Timeframe + Limit

Choose how far back to look (last_3_months, last_year, etc.) and how many headlines to fetch per company (max 1000).
4

Run It

Each article becomes a new row — companies with more coverage get more visibility.

​
Inputs

​
🛠️ Required Fields

  • Domain (✅)
    This is how we look up company-specific headlines.
    Example: nrev.ai or @domain (dynamic reference)
  • Timeframe (✅)
    Controls how recent the articles are.
    Options: last_month, last_3_months, last_6_months, last_year
  • Limit (✅)
    Sets the max number of headlines returned per company.
    Default is 100. Max: 1000 per domain.
    Each article = one row.

​
Output

You’ll get a row per article with the following fields:
  • title – The article headline
  • news_url – Direct link to the source
  • timestamp – When we detected it
FieldDescription
titleArticle headline
news_urlLink to original article
timestampWhen the article was detected
Get Company News output screenshot
If your input already has a column like title, we’ll rename the new one to avoid conflict (e.g., title_1).

​
How It Works

  1. We read the domain (static or via @)
  2. Query Predictleads for recent articles about that company
  3. Add each article as a separate row
  4. Auto-resolve naming conflicts so downstream steps aren’t blocked

​
🚀 Use Cases & Prompts

Use CaseSetup Example
Warm OutboundUse @domain, fetch headlines, and mention recent press in email
Account ResearchSee who’s raising, hiring, or getting featured
Prioritization SignalsMore headlines = more market motion — maybe it’s time to reach out
Competitive MonitoringFetch news for rival accounts weekly

​
✨ Pro Tips

Use this with AI Scorer or Enrich Company — news can fuel prioritization, personalization, or signal-based routing.
After pulling news, export to CRM, route to reps, or plug into an AI writer for personalized outreach.
Your column names are safe — fields like title or timestamp get auto-suffixed when needed.

​
⚠️ Important Considerations

No domain = no news — if a row has a blank or broken domain, we skip it silently.
Multiple articles = multiple rows — plan downstream filters or grouping accordingly.
Limit sets a max per company — if you need fewer articles, adjust the dropdown.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
Blank outputNo news for that domainTry expanding the timeframe or check the domain
title_1, timestamp_1Column name collisionUse Rename Columns downstream if needed
Too many rowsCompany has lots of coverageAdjust the limit field or filter later

​
📝 FAQ

Right now, all news is powered by Predictleads. We’re exploring more sources to expand coverage.
Nope — you’re only charged for domains where news was actually fetched.
Yes — each row in your input table can reference a different domain.
You choose the recency. We offer filters for last 1, 3, 6, or 12 months.

​
💰 Pricing

ModeCredit Cost
Per page fetched2 credits
You’re only charged for domains where headlines are actually returned — no results = no cost.

Enrich your accounts with timely context — use recent headlines to drive better targeting, scoring, or outreach. 📰📊