apify-financial-news

작성자: apify

추적 중인 포트폴리오 기업에 대한 금융 뉴스를 33개의 검증된 티어 1 소스(블룸버그, 로이터, FT, WSJ, 인텔리뉴스, Č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
인스타그램 브랜드-크리에이터 파트너십을 Apify 액터를 연결하여 발견하세요. 사용자가 브랜드와 협업하는 사람, 크리에이터가 유료로 진행한 브랜드 등을 물을 때 사용하세요.
official
dig
apify
Apify MCP 서버에서 작업을 탐색, 계획 및 사양을 정하는 유연한 스킬입니다. 소스 파일을 편집하지 마십시오 — 이 스킬은 이해와 계획 전용입니다.
official
apify-actor-development
apify
서버리스 클라우드 프로그램을 생성, 디버깅 및 배포하여 웹 스크래핑, 자동화 및 데이터 처리를 수행합니다. JavaScript, TypeScript 및 Python 템플릿을 지원하며, HTTP 및 브라우저 기반 크롤링을 위한 통합 Crawlee, Playwright 및 Cheerio 라이브러리를 포함합니다. 격리된 스토리지와 함께 apify run을 통한 로컬 테스트, 입력/출력에 대한 스키마 검증, apify push를 통한 Apify 플랫폼 배포를 포함합니다. Apify CLI 인증 및 AI를 위한 .actor/actor.json의 필수 generatedBy 메타데이터가 필요합니다...
official
apify-actorization
apify
기존 프로젝트를 언어별 SDK 통합을 통해 서버리스 Apify Actor로 변환합니다. 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
Instagram, TikTok, YouTube, Facebook, Google Maps 등 55개 이상의 플랫폼에 최적의 Actor를 선택하는 자동화된 웹 스크래퍼. 8개 주요 플랫폼에 걸쳐 55개 이상의 사전 구성된 Actor를 포함하며, 사용 사례별 선택 가이드(리드 생성, 인플루언서 발굴, 브랜드 모니터링, 경쟁사 분석, 트렌드 조사)를 제공합니다. 빠른 채팅 표시, CSV 내보내기, 또는 사용자 정의 가능한 결과 제한이 있는 JSON 내보내기의 세 가지 출력 형식을 지원합니다. 복잡한 작업을 위한 다중 Actor 워크플로 패턴을 포함합니다...
official
apify-audience-analysis
apify
페이스북, 인스타그램, 유튜브, 틱톡에서 잠재 고객 인구통계, 참여 패턴, 행동 데이터를 추출합니다. 4개 플랫폼 전반에 걸쳐 팔로워 인구통계, 참여 지표, 댓글, 프로필 분석을 다루는 18개 이상의 전문 액터를 지원합니다. 빠른 채팅 표시, CSV 내보내기, 다운스트림 분석용 JSON 내보내기 등 세 가지 출력 형식을 제공합니다. Apify 토큰과 mcpc CLI 도구가 필요하며, 동적 스키마 가져오기를 사용하여 각 액터의 요구사항에 맞게 입력을 조정합니다. 구조화된...
official