TradingView Ideas & Strategy Scraper

Collect publicly visible TradingView community Ideas into a structured dataset.

No TradingView login, personal feed, or trading account is required.

Use it to turn public charts, strategy notes, author activity, and engagement into research-ready rows.

What does it do?

This scraper visits public TradingView Ideas feeds, symbol pages, category pages, and author pages.

It saves one record for each visible community Idea.

Records include a title, chart link, symbol, author, publishing time, visible strategy direction, excerpt, comments, boosts, and chart image URL.

Optional enrichment visits the public Idea page for additional metadata when available.

Who is it for?

Investment-research analysts can monitor a public symbol feed without manually copying cards.

Quant-research teams can build a repeatable public-signal dataset for offline analysis.

Trading-content teams can track author activity, themes, and community engagement.

Market-intelligence teams can preserve public editorial ideas with collection provenance.

Why use it?

TradingView cards are useful for browsing but difficult to filter, compare, or export at scale.

This actor converts the visible public information into JSON, CSV, Excel, or an API dataset.

Each record retains its source URL so a researcher can inspect the original public page.

Public-only scope

The actor only requests public TradingView pages.

It does not sign in, use cookies from your account, access watchlists, create alerts, or place trades.

Do not submit private or authenticated URLs.

Data you receive

Field	Description
ideaUrl	Public chart/Idea URL
title	Visible Idea title
symbol	Visible market symbol when shown
author	Public author name
publishedAt	Card publication timestamp
direction	Visible Long or Short signal when shown
descriptionExcerpt	Public card/detail description
comments	Visible comment count
likes	Visible boost count
chartImageUrl	Public preview image URL

Quick start

1. Add https://www.tradingview.com/ideas/ as a public source URL.

2. Set maxItems to 10 for a first run.

3. Run the actor.

4. Export the dataset or connect it to your analysis workflow.

Input: public source URLs

Use a public Ideas page as the most predictable collection source.

Examples include the Ideas landing page, a public symbol Ideas page, a public category page, or a public author page.

The actor validates that URLs belong to tradingview.com and are public Idea-related paths.

Input: keyword

A keyword produces a best-effort public Ideas query.

For recurring production workflows, prefer a stable source URL because public site search can change.

Leave the keyword blank when using source URLs.

Input: maximum Ideas

maxItems limits saved records from 1 through 500.

Start with 10 to confirm that a chosen source returns the public cards you expect.

Increase it only after checking the output quality.

Input: detail enrichment

Enable enrichDetails to visit public Idea pages after parsing feed cards.

This can add public description, image, and timing metadata.

It is slower than feed-only collection.

If a detail page is unavailable, the actor keeps the already-collected feed record.

Output example

{
  "title": "XAU SHORT$",
  "symbol": "OANDA:XAUUSD",
  "author": "JupahduhX",
  "direction": "Short",
  "comments": 69,
  "ideaUrl": "https://www.tradingview.com/chart/XAUUSD/.../"
}

Interpreting engagement

comments is the visible public comment count.

likes records the public card’s visible boost count where TradingView exposes it.

views and tags are optional because they are not present on every public layout.

Null means the field was not publicly displayed, not that the actor guessed a value.

Soft block behavior

Public sites can filter, redesign, or temporarily rate-limit individual pages.

The actor logs a warning and skips an unavailable feed rather than discarding records saved from other feeds.

A successful run can therefore contain partial results when one source is unavailable.

Tips for research quality

Use one symbol or author source per recurring job for clean provenance.

Keep feed-only runs for broad monitoring.

Use detail enrichment for smaller, higher-value investigations.

Store collectedAt alongside publishedAt when measuring recency.

Integrations

Send the dataset to Google Sheets for an analyst review queue.

Use a webhook to trigger a research-notebook import after each run.

Join symbol, author, and publishedAt with your internal signal or content database.

Use the Apify API to load rows into Python, R, or a warehouse.

API usage: Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/tradingview-community-ideas-strategy-scraper').call({
  startUrls: [{ url: 'https://www.tradingview.com/ideas/' }], maxItems: 10
});
console.log(await client.dataset(run.defaultDatasetId).listItems());

API usage: Python

from apify_client import ApifyClient
client = ApifyClient()
run = client.actor('automation-lab/tradingview-community-ideas-strategy-scraper').call(run_input={
    'startUrls': [{'url': 'https://www.tradingview.com/ideas/'}], 'maxItems': 10
})
print(list(client.dataset(run['defaultDatasetId']).iterate_items()))

API usage: cURL

curl "https://api.apify.com/v2/acts/automation-lab~tradingview-community-ideas-strategy-scraper/runs?token=$APIFY_TOKEN" \
  -H 'content-type: application/json' \
  -d '{"startUrls":[{"url":"https://www.tradingview.com/ideas/"}],"maxItems":10}'

MCP for AI assistants

Use this actor through Apify MCP in Claude Code or Claude Desktop.

Add https://mcp.apify.com?tools=automation-lab/tradingview-community-ideas-strategy-scraper to your MCP configuration.

For Claude Code, add the server with:

$claude mcp add apify --transport http 'https://mcp.apify.com?tools=automation-lab/tradingview-community-ideas-strategy-scraper'

For a JSON MCP client configuration:

{"mcpServers":{"apify":{"url":"https://mcp.apify.com?tools=automation-lab/tradingview-community-ideas-strategy-scraper"}}}

Example prompt: “Collect 20 public TradingView Ideas from this symbol page and summarize visible Long/Short direction by author.”

How much does it cost to scrape TradingView Ideas?

The actor uses pay-per-event pricing: a small start event plus a per-record event.

Higher-volume tiers receive automatic discounts.

Check the actor’s live pricing panel before a production run because platform pricing is authoritative.

Legality and responsible use

Collect only public data and comply with TradingView’s terms, robots guidance, and applicable law.

Do not use the output as financial advice or as a basis for automated trading execution.

Respect applicable data-protection and intellectual-property obligations.

Troubleshooting: no records

Confirm the URL is public and opens in a logged-out browser.

Try the Ideas landing page first, then use a source URL copied from the public site.

A layout change or unavailable source can produce a warning with zero records.

Troubleshooting: missing fields

Public card layouts vary by Idea and locale.

Fields such as direction, views, tags, and timeframe are optional and remain null or empty when not shown.

Enable detail enrichment for smaller collections when you need richer public metadata.

FAQ: can I use a TradingView account?

No. This actor intentionally does not accept credentials or access private account data.

FAQ: does it give trading advice?

No. It collects publicly visible content for research and content workflows.

FAQ: can I monitor authors?

Yes. Submit a public TradingView author URL as a source and schedule a recurring run.

Related scrapers

For public market-screening rows rather than community/editorial Ideas, see the TradingView Scraper.

For a broader automation portfolio, browse Automation Lab actors.

Support

Include the public source URL, run ID, and a small sample of expected public cards when reporting a parsing issue.

That helps distinguish a page-layout change from a source-specific availability problem.