X (Twitter) Trends Scraper

See what is trending on X (Twitter) in any country or city, and how long each trend has been trending. Every row carries its best rank in the last 24 hours, hours on the list, when it first appeared, and where else it is trending. No X account, no API key.

At a glance
You give it	Locations: worldwide, countries or cities
You get	One row per trend: rank, best rank in 24 hours, hours trending, first seen, where else it trends
Price	$0.0026 per run + $0.0002 per trend (Free plan, lower on paid plans)
Speed	Five countries in about 7 seconds
Needs	Nothing: no login, no API key, no proxy

What you get

• Current trends for worldwide, 60+ countries, and cities (New York, US, united-kingdom/london), up to 50 per location.
• Recent history on every trend: hoursTrending24h, bestRank24h, firstSeenAt, and isNew for topics that just broke onto the list, from the last 24 hourly snapshots (about 20 hours). Spot what is rising versus what has been there all day.
• Cross-location overlap: locationCount, locationsTrendingIn, bestRankAcrossLocations across all locations in the run.
• Full hourly history (optional): every hourly snapshot the source keeps (about the last 20 hours), about 1,100 rows per location.
• Fast and light: five countries took 7 seconds; 100 trends used $0.0007 of platform usage.

Freshness: trends come from snapshots of X's trending list taken about every 52 minutes, so the current list can be up to about an hour old. The source keeps the last 24 snapshots, so history fields cover roughly the last 18 to 20 hours, not a full 24. In a side-by-side test against a live X source, 42 to 44 of the 50 trends matched; the rest had rotated since the last snapshot.

Use cases

• Newsjacking and social media marketing. Catch a trend in its first hour (isNew) and post while it is rising.
• Brand safety. Know what is trending before a campaign goes out.
• Media and research dashboards. Hourly trend history by country, for charts and reports.
• Cross-market comparison. Which topics trend in the US and the UK at once, and which are local.
• Alerts. Tell me when a keyword or hashtag starts trending anywhere.

Example inputs

Trends right now

{ "locations": ["worldwide", "US", "UK", "India"] }

Cities

{ "locations": ["New York, US", "Los Angeles, US", "united-kingdom/london"], "maxTrendsPerLocation": 20 }

Full hourly history for one country

{ "locations": ["US"], "includeHistory": true }

Input

Field	What it does
locations	worldwide, a country code (US, UK, JP...), a country name, City, Country, or country/city.
maxTrendsPerLocation	1 to 50. Default 50.
includeHistory	Every hourly snapshot the source keeps (up to 24, about the last 20 hours) instead of just the current list.

Output

A real row from a test run on 2026-09-26:

{
  "rank": 1,
  "name": "#YouManiacSeriesEP5",
  "isHashtag": true,
  "searchUrl": "https://x.com/search?q=%23YouManiacSeriesEP5",
  "location": "worldwide",
  "locationSlug": "worldwide",
  "snapshotAt": "2026-09-26T16:03:20Z",
  "bestRank24h": 1,
  "hoursTrending24h": 7,
  "firstSeenAt": "2026-09-26T10:51:34Z",
  "isNew": false,
  "locationCount": 2,
  "locationsTrendingIn": [
    "worldwide",
    "US"
  ],
  "bestRankAcrossLocations": 1
}

With includeHistory on, each row is one trend in one hourly snapshot: rank, name, isHashtag, searchUrl, location, locationSlug, snapshotAt. The history and cross-location fields are left out, because they describe the current list only.

Field meanings:

• hoursTrending24h: number of hourly snapshots (out of up to 24) the trend appears in.
• bestRank24h and firstSeenAt: best rank and first appearance within those snapshots.
• isNew: the trend is only in the newest snapshot.
• locationCount, locationsTrendingIn, bestRankAcrossLocations: across the locations in this run only.

Pricing

Pay per event:

• $0.0026 per run start
• $0.0002 per trend row on the Free plan (lower on higher Apify plans)

Apify platform usage is billed separately to your account and is tiny: 100 trends used $0.0007.

What you scrape	Actor cost
Worldwide + US (100 trends)	about $0.023
10 countries (500 trends)	about $0.10
1 country, full history (about 1,100 rows)	about $0.22

Automate it with n8n

Each workflow uses n8n's official Apify node, operation Run actor and get dataset, actor labrat011/x-trends-scraper. Paste the input into Input JSON.

1. New trend alert to Slack (hourly)

Schedule Trigger (every hour)
  > Apify: Run actor and get dataset   { "locations": ["US"], "maxTrendsPerLocation": 20 }
  > Filter: isNew is true
  > Slack: "New on X in the US at #{{ $json.rank }}: {{ $json.name }} {{ $json.searchUrl }}"

2. Keyword watch across countries

Schedule Trigger (every hour)
  > Apify: Run actor and get dataset   { "locations": ["worldwide", "US", "UK", "CA", "AU", "IN"] }
  > Filter: name contains "yourbrand" (case-insensitive)
  > Email / SMS: "Trending in {{ $json.locationsTrendingIn.join(', ') }}"

3. Trend history dashboard

Schedule Trigger (every 12 hours)
  > Apify: Run actor and get dataset   { "locations": ["US", "UK"], "includeHistory": true }
  > Google Sheets / BigQuery: append rows, skipping ones already stored (key: location + snapshotAt + rank)
  > Looker Studio: chart rank over time per topic

4. AI content ideas from trends

Schedule Trigger (twice a day)
  > Apify: Run actor and get dataset   { "locations": ["US"], "maxTrendsPerLocation": 30 }
  > Filter: hoursTrending24h <= 3 (fresh topics only)
  > OpenAI / Anthropic: "Which of these fit our brand (describe it)? Suggest a post for each."
  > Notion: save the ideas for the social team

5. Global vs local topics report

Schedule Trigger (weekly)
  > Apify: Run actor and get dataset   (10 countries)
  > Filter: locationCount >= 3
  > Google Docs: "Topics trending in 3+ countries this week"

For AI agents

• Actor: labrat011/x-trends-scraper
• Smallest input: { "locations": ["worldwide"] }
• One row = one trend in one location at the snapshot time. Key fields: rank, name, location, snapshotAt, bestRank24h, hoursTrending24h, locationsTrendingIn.
• Billing: apify-actor-start once per run, trend per row. Cap spend with maxTrendsPerLocation or a maximum cost per run.
• Run it: POST https://api.apify.com/v2/acts/labrat011~x-trends-scraper/run-sync-get-dataset-items with the input as the JSON body, or call it from the Apify MCP server.
• Done signal: the run's status message reads Saved N trends from L locations in R requests. Locations with no data are listed after No data for:. If no location has data, the run fails instead of returning an empty dataset.

FAQ

Why is tweet volume not included? X stopped showing reliable tweet counts on its public trends. Rather than return empty columns, this actor gives you rank history and spread across locations instead.

How fresh is the data? Trends refresh about hourly. snapshotAt on every row says exactly when the list was taken.

Why is it called 24h if it covers about 20 hours? The source keeps the last 24 snapshots, taken about every 52 minutes. The field names count snapshots; the time they span is about 18 to 20 hours. Repeat snapshots taken seconds apart are dropped so they do not inflate the counts.

Which cities are supported? Most large cities X tracks. Use City, Country (Chicago, US) or the path form (united-states/chicago). A location with no data is named in the run log and the status message, and is not charged. A few countries (for example Bangladesh) are not covered by the source.

Support

Open an issue on the actor's Issues tab with the run ID and it will be looked at.