X.com (Twitter) Community Post Scraper

Scrape posts from any X.com (formerly Twitter) Community. Paste a community URL and get thousands of confirmed community posts straight to your spreadsheet, CRM, or dashboard.

🐦 What it does

Give it one or more community URLs (or 19-digit community IDs) and this tool returns every post it can confirm belongs to that community.

For every post you get:

• The full post text (no 280-character truncation on long-form notes)
• Author handle, display name, and follower and following counts
• Likes, retweets, quotes, replies, and view counts
• Attached photos and videos (turn on the download add-on to save the files)
• Precise creation timestamp in ISO 8601
• The community ID the post belongs to

📋 How to use it

Step 1: Provide community URLs or IDs

Paste one or more of these into the input:

• Community URL: https://x.com/i/communities/1493446837214187523
• Bare 19-digit ID: 1493446837214187523

Grab either from any X community page. Click "Communities" in the X sidebar, open a community, and copy the URL bar or the number after /i/communities/.

You can mix URLs and IDs in one run.

Step 2: Set the limit and sort

• Max posts per run: hard cap on how many posts the run returns across every input community. Default is 100 to protect against surprise bills. Raise as high as you need. On an active community, expect around 1,000 to 1,500 posts per run.
• Sort posts by: pick Newest for chronological or Most engaged for likes plus retweets first.

Step 3: (Optional) Filter your results

• Minimum likes, retweets, replies, or views: drop posts below your threshold.
• Exclude replies / retweets: keep timelines clean.
• Must have media: keep only posts with an attached photo or video.

Filters are free. Posts that get filtered out are never billed.

Step 4: (Optional) Add-ons

Every add-on is off by default. Each one is billed only when it returns a real result. Failed lookups cost nothing.

• Community metadata: adds one row per community with the community's rules, trending hashtags, member count, creator, banner, join policy, and topic. Billed once per community successfully resolved.
• Download media files: saves every photo and video attached to a post into your run's key-value store. You get a signed download link on each media item. Billed once per post that had at least one file saved.

Step 5: Run

Click Start. Rows stream into the Output tab as each round finishes, so you do not have to wait for the whole run.

📊 What you get

Every row has a rowType column so you can tell at a glance whether it is a post or a community metadata row. Four tabs group the fields by what you probably care about:

Tab	What is in it
🔎 Overview	Row type, status, community name, URL, text, author, top counts, date
📝 Posts	Full post spread: every engagement count, media, author block, community ID
🏛️ Communities	Community metadata rows (with the metadata add-on): name, description, member count, rules, trending hashtags, creator, banner
🎬 Media	Posts that have media, with a signed download link per file when the download add-on is on

You can export from the Output tab as JSON, CSV, or Excel.

Every row has a status field. Success means the row is good. Anything else is a human-readable message explaining what happened (community not found, community private, X temporarily unavailable). Rows that did not succeed are never billed.

💰 Pricing

You only pay for what you get. Every event is billed per result.

Event	Rate	When it fires
Actor run start	$0.00005	Once per run
Post scraped	$0.30 / 1,000	Once per unique post row
Community metadata (add-on)	$0.02 per community	Once per community successfully resolved with the metadata add-on on
Media download (add-on)	$2.00 / 1,000	Once per post with at least one file saved

💡 Good to know

• Long text is never truncated. Long-form notes come back in full.
• URL forms accepted: x.com/i/communities/<id> and the bare 19-digit ID both work.
• On active communities, expect roughly 1,000 to 1,500 posts per run. Very small or brand new communities may return fewer.
• Media files are stored in your Apify key-value store. How long they are kept depends on your Apify plan.
• Rows appear in real time. You can open the Output tab while the run is still going and start pulling data.

For developers

You can call this actor through the Apify API:

{
    "communityUrls": [
        "https://x.com/i/communities/1493446837214187523",
        "1699807431709041070"
    ],
    "maxItems": 500,
    "sortPostsBy": "Newest",
    "minLikes": 10,
    "excludeReplies": true,
    "extractCommunityMetadata": true,
    "extractMedia": true
}

Provide at least one entry in communityUrls. All other fields are optional.

❓ FAQ

How many posts do I get per community? On an active community, around 1,000 to 1,500 posts per run. Very small or brand new communities return fewer, since there are simply fewer active posters.

Can I filter by author, hashtag, or date range? You can filter by minimum likes, retweets, replies, and views. You can exclude replies or retweets and require attached media. You can sort by newest or most engaged. Author and date filters are not supported today.

Can I use my own X cookies? No. This actor does not accept user cookies.

Why does one of my communities return fewer posts than another? Community post yield depends on how many people post in it and how public their profiles are. A tightly moderated small community will return fewer posts than a large active one.

How long are downloaded media files stored? Files land in your Apify key-value store. Retention depends on your Apify plan.

🔗 Other tools you might like

• X.com (Twitter) Tweet Scraper: scrape tweets by handle, URL, or search query.
• X.com (Twitter) Thread Unroller & Scraper: expand full conversation threads.
• X (Twitter) Video, Photo & GIF Downloader: download photos, videos, and GIFs from any tweet.
• X.com (Twitter) Profile Scraper: pull full profile data for any handle.
• X.com (Twitter) Tweet Replies Scraper: grab every reply to any tweet.

⚖️ Disclaimer

This tool is intended for personal, research, and educational use. You are responsible for complying with X.com's Terms of Service and applicable laws in your jurisdiction. The developer is not liable for misuse. Data availability depends on X at run time.

Keywords: twitter community scraper, x community scraper, twitter communities, x communities, community posts, community scraper, twitter scraper, x.com scraper