apify-financial-news

作者: apify

Discover and extract financial news for tracked portfolio companies across 33 verified Tier 1 sources (Bloomberg, Reuters, FT, WSJ, IntelliNews, ČTK, PAP, BTA,…

npx skills add https://github.com/apify/awesome-skills --skill apify-financial-news

Financial News Intelligence

Discover and extract financial news for portfolio companies via Apify Actors. Two modes:

  • Single company — news scan for one company.
  • Portfolio scan — same pipeline run across multiple companies.

33 Tier 1 sources organized in 4 categories (Global / Pan-European / Institutional / CEE Local). Tier 2 = broad Google News fallback for unverified domains.

Estimated cost: $0.10–0.50 per single company, $1–5 per full portfolio scan.

Prerequisites

  • Apify access — preferred: apify CLI (npm install -g apify-cli && apify login); fallback: Apify MCP connector (call-actor tool). CLI is faster and preferred when both are available.
  • Python 3 + pip install readability-lxml lxml (for the extract_and_clean.py post-processor)
  • Companies data at ${CLAUDE_PLUGIN_ROOT}/data/companies.json

${CLAUDE_PLUGIN_ROOT} is the plugin's root directory (where .claude-plugin/ lives). It is resolved automatically by Claude Code when the plugin is installed, or set to the --plugin-dir path during development.

Workflow checklist

Copy this and tick boxes as you progress:

Task Progress:
- [ ] Step 0: Verify prerequisites — try `apify --version && apify info`; if unavailable, check for `call-actor` MCP tool; if neither, tell user to install apify CLI or Apify MCP connector. Also verify: `python3 -c "from readability import Document; print('OK')"` (install: `pip install readability-lxml lxml`)
- [ ] Step 1: Build queries (look up company in data/companies.json or construct manually)
- [ ] Step 2: Discovery — pick 8-12 sources by region, run 2-phase Google News
- [ ] Step 3: Dedup + route (Tier 1 = whitelisted domain → verified extractor; Tier 2 = broad → rag-web-browser)
- [ ] Step 4: Extract & clean (run extractor, then extract_and_clean.py)
- [ ] Step 5: Output Tier 1 + Tier 2 tables to user

Constraints

Allowed Apify Actors (exhaustive — do NOT use others)

ActorPurpose
data_xplorer/google-news-scraper-fastGoogle News discovery
louvre/rss-news-aggregatorRSS discovery
rodrigo_pacelli/headline-news-scraperHeadline discovery
jamie_tran/bloomberg-article-scraperBloomberg extraction
romy/bloomberg-news-scraperBloomberg fallback
workhard3000/news-intelligence-rag-extractorPaywall extraction
apify/rag-web-browserFree/soft-paywall + Tier 2
stanvanrooy6/universal-ai-web-scraperHard paywall (Barron's, MarketWatch) — $0.25/page

Do NOT use any other actor. Do NOT use WebSearch, WebFetch, or browser tools.

Extractor routing (mandatory — do NOT substitute)

ExtractorDomains
jamie_tran/bloomberg-article-scraperbloomberg.com
workhard3000/news-intelligence-rag-extractorft.com, wsj.com, economist.com, morningstar.com, asia.nikkei.com, caixinglobal.com, zawya.com, euobserver.com, reuters.com
apify/rag-web-browsercnbc.com, forbes.com, investors.com, lesechos.fr, afr.com, scmp.com, euronews.com, intellinews.com, handelsblatt.com, politico.eu, eubusiness.com, eureporter.co, ecb.europa.eu, + all 7 CEE Local
stanvanrooy6/universal-ai-web-scraperbarrons.com, marketwatch.com
REST API (presscorner)ec.europa.eu

Full per-source config: reference/SOURCE_CONFIGS.md. Machine-readable: data/sources.json.

Pipeline

Step 1: Build queries

Look up company in ${CLAUDE_PLUGIN_ROOT}/data/companies.json. Key fields under queries: gnews_en, gnews_cz, bloomberg.

For non-portfolio companies, construct manually: quoted full legal name + ticker OR variant + geographic qualifier.

Query rules:

  • Use "InPost SA" not InPost (quoted full names avoid false positives — see reference/EUROPEAN_COMPANIES_GUIDE.md)
  • Per-source site: operator: site:bloomberg.com "InPost SA" OR "INPST"
  • FT tip: use site:ft.com/content/ (bare ft.com returns stock-data pages)
  • Valid timeframes: "1h", "1d", "7d", "1y", "all" (NOT "30d")
  • Tickers < 4 chars: always pair with full company name
  • ALWAYS set decodeUrls: true on Google News input

Step 2: Discovery

Do NOT search all 33 sources. Pick 8–12 based on company region.

Regional priorities

RegionPriority Sources
CZČTK, IntelliNews, Reuters, Bloomberg, POLITICO EU, FT, Handelsblatt
PLPAP, IntelliNews, Reuters, Bloomberg, POLITICO EU, FT
HUTelex.hu, HVG.hu, VG.hu, IntelliNews, Reuters, Bloomberg
BGBTA, IntelliNews, Reuters, Bloomberg, Euronews
SKTASR, IntelliNews, Reuters, Bloomberg, Handelsblatt
Western EuropeBloomberg, Reuters, FT, Handelsblatt, Les Echos, POLITICO EU
US / GlobalBloomberg, Reuters, WSJ, FT, CNBC, Forbes, Barron's
Asia / MENABloomberg, Reuters, SCMP, Nikkei, Caixin, Zawya
EU RegulatoryPOLITICO EU, EUobserver, EUbusiness, EU Reporter, EC Press Corner, ECB

Two-phase Google News strategy

Phase 1 — Targeted (per priority source, with site:):

apify call data_xplorer/google-news-scraper-fast \
  --input '{"keywords":["site:bloomberg.com \"InPost SA\" OR \"INPST\""],"maxArticles":10,"timeframe":"7d","region_language":"US:en","decodeUrls":true,"proxyConfiguration":{"useApifyProxy":true,"apifyProxyGroups":["RESIDENTIAL"]}}' \
  --user-agent apify-awesome-skills/apify-financial-news \
  --output-dataset > discovery_bloomberg.json

Phase 2 — Broad (always run, no site: operator). Classify results by domain in Step 3 — whitelisted → Tier 1, others → Tier 2.

CEE local-language discovery: For CEE companies, run additional queries with region_language set to CZ:cs, PL:pl, HU:hu, BG:bg, SK:sk. See region_language field per source in data/sources.json.

EC Press Corner — direct REST API (no Actor)

curl -s "https://ec.europa.eu/commission/presscorner/api/documents?reference=IP/26/614&language=en"

Parse IP_XX_NNN reference IDs from Google News titles to construct API calls.

RSS / Headline discovery (optional)

For sources with RSS, you can supplement GNews with louvre/rss-news-aggregator (max 10 feeds per run; split into batches). For 6 sources, rodrigo_pacelli/headline-news-scraper works (CNBC, SCMP, Nikkei, Caixin, Zawya tag-pages-only, Handelsblatt). RSS/headline output is unfiltered — filter client-side by company name in title/description. Full feed list: reference/PIPELINE_DETAIL.md.

Step 3: Dedup & route

  1. Collect URLs from all discovery runs.
  2. Classify by domain: whitelist (33 Tier 1 sources) → Tier 1; other → Tier 2.
  3. Filter non-article URLs: /quote/, /stock/, /sitemap, /author/, /tag/, /key-metrics/, /newsletters/, /topic/, /profile/, redirectUrl=.
  4. Filter by company name/ticker in title.
  5. Deduplicate (URL normalize).
  6. Route Tier 1 URLs to verified extractor per routing table.
  7. Route Tier 2 URLs to apify/rag-web-browser.

Low-coverage fallback (< 3 articles): broaden timeframe to "1y", run Phase 2 if skipped, try local-language queries.

Step 4: Extract & clean

Run the extractor per the routing table. For rag-web-browser calls, use outputFormats: ["html"].

After extraction, run extract_and_clean.py on the dataset to strip nav/menus/footers via readability-lxml. The script auto-detects format: HTML cleaned via readability-lxml, already-clean output (Bloomberg scraper, workhard3000) passes through.

DATASET_ID=$(apify call apify/rag-web-browser \
  --input '{"query":"<ARTICLE_URL>","maxResults":1,"outputFormats":["html"],"requestTimeoutSecs":40,"proxyConfiguration":{"useApifyProxy":true,"apifyProxyGroups":["RESIDENTIAL"]},"removeCookieWarnings":true}' \
  --user-agent apify-awesome-skills/apify-financial-news \
  --json | jq -r '.defaultDatasetId')

python3 ${CLAUDE_PLUGIN_ROOT}/skills/apify-financial-news/reference/scripts/extract_and_clean.py "$DATASET_ID"

The --json flag returns run metadata including defaultDatasetId. Errors produce non-zero exit code so the pipeline fails fast.

Step 5: Output

Two tables to the user — Tier 1 (verified) and Tier 2 (broad). Per article: source, title, author, date, char count, URL.

## News Intelligence: InPost (INPST.AS) — Last 7 days

### Tier 1 — Verified Sources (2)
| Source | Title | Author | Date | Chars | URL |
|--------|-------|--------|------|-------|-----|
| bloomberg.com | InPost Readies AI Shopping Assistant | K. Krasuski | 2026-03-19 | 7,577 | … |

### Tier 2 — Broad Discovery (5)
| Source | Title | Date | Chars | URL |
|--------|-------|------|-------|-----|
| seekingalpha.com | InPost expands parcel locker network | 2026-03-18 | 1,200 | … |

*Sources: 6 verified queried | 5 broad | Cost: $0.15*

Macro context

For country-level economic context, use these alongside news scans:

  • ING Think (think.ing.com) — daily CEE FX/rates via apify/rag-web-browser (~11K chars). Best free open-access CEE macro source.
  • IMF (imf.org) — Article IV concluding statements via apify/rag-web-browser (~22K chars).
  • ECB (ecb.europa.eu) — already in Tier 1.
  • Central banks (ČNB, NBP, MNB, BNB, NBS) — direct URL extraction; see reference/MACRO_SOURCES.md.

Critical gotchas

  • ALWAYS decodeUrls: true in Google News (encoded redirects break ALL extractors).
  • "InPost" is ambiguous — matches "post-Maduro". Use "InPost SA" for precision.
  • RSS max 10 feeds per run — split into batches.
  • Zawya headline-scraper returns tag pages, NOT articles — exclude from headline runs.
  • Reuters needs RESIDENTIAL proxy — without it, returns 386 chars.
  • Reuters: rag-web-browser returns 0 chars on ~60% of URLs — use workhard3000 only.
  • Morningstar .co.uk URLs fail with workhard3000 — use .com URLs for extraction.
  • WSJ livecoverage pages fail — skip URLs matching wsj.com/livecoverage/.
  • FT: rag-web-browser returns 16 chars ('Client Challenge') — use workhard3000.
  • Forbes: workhard3000 returns 0 chars — use rag-web-browser.
  • Barron's / MarketWatch cost $0.25/page — use selectively for high-value articles.
  • Caixin URLs must be complete — truncated URLs fail extraction.
  • EC Press Corner is an Angular SPArag-web-browser returns 0 chars. Use REST API.

Full failure-mode catalog: reference/PIPELINE_DETAIL.md, reference/SOURCE_CONFIGS.md.

Reference

來自 apify 的更多技能

bug-triage
apify
分類處理 apify/apify-mcp-server 上的未解決錯誤問題。分析、草擬回覆、取得批准、發布。
official
apify-influencer-brand-collabs
apify
Discover Instagram brand–creator partnerships by chaining Apify Actors. Use when the user asks who collabs with a brand, which brands a creator has done paid…
official
dig
apify
用於在 Apify MCP 伺服器上探索、規劃與規格化工作的靈活技能。請勿編輯原始檔案——此技能僅供理解與規劃使用。
official
apify-actor-development
apify
建立、除錯及部署無伺服器雲端程式,用於網頁爬取、自動化及資料處理。支援 JavaScript、TypeScript 及 Python 範本,內建 Crawlee、Playwright 與 Cheerio 函式庫,適用於 HTTP 及瀏覽器爬取。包含透過 apify run 進行本地測試(具備隔離儲存)、輸入/輸出結構驗證,以及透過 apify push 部署至 Apify 平台。需進行 Apify CLI 驗證,並在 .actor/actor.json 中強制加入 generatedBy 元資料以供 AI 使用...
official
apify-actorization
apify
將現有專案轉換為無伺服器 Apify Actors,並整合語言專屬 SDK。支援 JavaScript/TypeScript(使用 Actor.init() / Actor.exit())、Python(非同步上下文管理器),以及透過 CLI 包裝器的任何語言。提供結構化工作流程:使用 apify init 建立專案骨架、套用 SDK 包裝、設定輸入/輸出架構、以 apify run 進行本地測試,再透過 apify push 部署。包含輸入與輸出架構驗證、Docker 容器化,以及可選的按事件付費...
official
apify-generate-output-schema
apify
為 Apify Actor 分析其原始碼,生成輸出結構(dataset_schema.json、output_schema.json、key_value_store_schema.json)。用於…
official
apify-ultimate-scraper
apify
自動化網頁爬蟲,為55多個平台選擇最佳Actor,包括Instagram、TikTok、YouTube、Facebook、Google地圖等。涵蓋8大主要平台的55多個預配置Actor,並提供針對特定使用案例的選擇指引(潛在客戶開發、網紅發現、品牌監控、競爭對手分析、趨勢研究)。支援三種輸出格式:快速聊天顯示、CSV匯出或JSON匯出,並可自訂結果數量限制。包含多Actor工作流程模式,適用於複雜...
official
apify-audience-analysis
apify
從Facebook、Instagram、YouTube和TikTok提取受眾人口統計、互動模式及行為數據。支援18個以上專業Actor,涵蓋四個平台的粉絲人口統計、互動指標、留言及個人檔案分析。提供三種輸出格式:快速聊天顯示、CSV匯出或JSON匯出供後續分析。需使用Apify token及mcpc CLI工具;透過動態架構擷取來調整輸入以符合各Actor需求。包含結構化...
official