X Posts scraper

What it collects

socialProxy advised

Everything an account has posted — text, timestamps, likes, reposts, replies, quotes, bookmarks, hashtags, mentions and the links behind the t.co wrappers, a row per post. It is a scraper, which means the whole contract is: fill in the form, and one table comes back. No browser window opens, it costs none of your plan's automation slots, and the requests go out over plain HTTP carrying a real browser's TLS fingerprint.

At volume this target is sensitive to where the request leaves from, so pick a proxy on the run — it is advice at the form rather than a gate, and a run without one still starts. Whichever way it went, every row records it — see the provenance columns below.

What you give it — 6

The form the app draws, read out of the card itself. Each hint below is the one shown beside that field in the run dialog, so nothing here is a description of the product written separately from it.

The one answer it needs

twitterHandles

Accounts · list · required

nasa, @nasa, the profile URL or a link to one of its posts all work. Each account is walked separately and the rows are pooled into one table, labelled by whose timeline they came from.

Everything else is optional

maxItems

Posts per account · number

Walked twenty at a time, so this rounds up to the next twenty. A protected account returns none however high this is set, and X stops serving a timeline long before it reaches the whole archive.

onlyPostsNewerThan

Only the last N days · number

Filters posts already collected, so it costs no extra request. Leave empty for everything the walk reaches.

minimumFavorites

Minimum likes · number

minimumRetweets

Minimum reposts · number

minimumReplies

Minimum replies · number

What comes back — 27 columns

One dataset per run — a typed table your workspace owns, which you can then sort, filter, edit in the grid, export whole, or read back over the local API. These are the columns it is created with.

23 from X Posts

4 that every scraper writes

The same four on every card, so a table can still answer months later how its rows got there: which service they came from, when, which profile's identity the requests carried, and whether that identity was signed in.

Four ways to run it

The Scrapers tab. Pick the card, fill in the form, press Start. Every run started here makes a new table, named after what you searched for and when. Check first if you like — it collects one page, writes nothing, and reports which columns came back filled.

Ask the assistant. It has the whole catalogue, so this card is a sentence rather than a form. It fills in the parameters above from what you said and shows you them before it starts.

Over MCP or the local API. The same card, from a coding agent — argus_run_scraper over the MCP server, or POST http://127.0.0.1:39219/v1/scrapers/run on the local API. There is a sample call beside it that writes nothing.

{
  "kind": "x_tweets",
  "inputs": {
    "twitterHandles": [
      "…"
    ]
  }
}

As a step inside a workflow. The Run scraper step puts this collector in the middle of an automation — collect, then filter, then mail — and the tree still opens no window doing it. It is also the one caller that can overrule the table-per-run rule: pointed at a table you name, it creates that table with the columns above if it is missing and files every run into it after, appending or updating the row in place on a column you match on. The step hands the next one the table's name, its id and the row count.

Where it stops

It will not drive a page. Anything that needs a real browser — a site with no list endpoint behind it, or anything operating an account of your own — is an automation instead, and that is a different tool rather than a worse version of this one.

It signs in to nothing. Reading a public page signed out is the settled position — Bright Data scraped Meta signed out and won; hiQ scraped LinkedIn signed in and lost — so this card asks for no account and holds none.