X (Twitter) Profile & Post Engagement Extractor: MCP config, n8n workflow and API

{
  "usernames": [
    "NASA"
  ],
  "include": [
    "profileInfo"
  ],
  "maxPostsPerProfile": 3,
  "includeReplies": false,
  "includeRetweets": false,
  "includeHighlights": false,
  "onlyWithMedia": false,
  "mediaType": "any",
  "onlyVerified": false,
  "verifiedType": "any",
  "minFollowers": 0,
  "maxFollowers": 0,
  "minAccountAgeDays": 0,
  "withWebsiteOnly": false,
  "activeWithinDays": 0,
  "enrichEngagement": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

---
name: x-twitter-profile-and-post-engagement-extractor
description: "One profile row per account, one post row per collected post (cursor-paged up to maxPostsPerProfile), and status rows for protected, missing, empty, filtered or limited accounts. Every row carries type, recordType, sourceUrl, collectedAt and scrapedAt. Runs the Apify Actor nimbryxo-studio/x-twitter-profile-and-post-engagement-extractor. Use when the user needs X (Twitter) data with fields such as type, recordType, status, message, username, name and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/x-twitter-profile-and-post-engagement-extractor"
  store-url: "https://apify.com/nimbryxo-studio/x-twitter-profile-and-post-engagement-extractor"
---

# X (Twitter) Profile & Post Engagement Extractor

Use this skill to fetch X (Twitter) data with the Apify Actor `nimbryxo-studio/x-twitter-profile-and-post-engagement-extractor` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `usernames` | array | Accounts to collect. Paste handles like `elonmusk`, `@apify`, profile links like `https://x.com/elonmusk`, numeric ids like `11348282` or `id:11348282`. Handles, links and ids can be mixed. |
| `include` | array | Pick one or more data groups. Everything works without cookies. `topPosts` is engagement-ranked from the candidate pool (X serves no public Top tab to guests). `replies` and `highlights` are best-effort: X sometimes refuses those guest timelines. |
| `maxPostsPerProfile` | integer | Target number of posts per account (1-1000). The actor follows X's guest timeline bottom cursor back to X's ceiling of about 3,200 posts; guest search top-ups are best effort. |
| `includeReplies` | boolean | Keep replies the account sent. Best effort: X only serves the reply timeline to logged-out callers on some attempts. |
| `includeRetweets` | boolean | Keep reposts in the results. Turn off to get only posts the account wrote itself. |
| `includeHighlights` | boolean | Also collect the account's curated Highlights tab. The guest legacy userId query pages the whole set through its bottom cursor (observed 100-1,097 rows on large accounts); the live one-page query remains a fallback. |
| `onlyWithMedia` | boolean | Keep only posts that contain media. |
| `mediaType` | one of `any`, `photos`, `videos`, `gifs` | Optional. Keep only posts with this media type. `media` in What to collect already limits rows to media posts. |
| `onlyVerified` | boolean | Skip accounts that do not carry a verified badge. |
| `verifiedType` | one of `any`, `blue`, `business`, `government` | Optional. Keep only accounts with this verification type. X and FxTwitter labels are normalized in code. |
| `minFollowers` | integer | Optional. Skip accounts below this follower count. 0 means any. |
| `maxFollowers` | integer | Optional. Skip accounts above this follower count. 0 means any. |
| `minAccountAgeDays` | integer | Optional. Skip accounts younger than this. 0 means any. Accounts without a public join date are skipped when this is set. |
| `withWebsiteOnly` | boolean | Skip accounts that expose no website link in their profile or bio. |

Example `input.json` (the Actor's published prefill):

```json
{
  "usernames": [
    "NASA"
  ],
  "include": [
    "profileInfo"
  ],
  "maxPostsPerProfile": 3,
  "includeReplies": false,
  "includeRetweets": false,
  "includeHighlights": false,
  "onlyWithMedia": false,
  "mediaType": "any",
  "onlyVerified": false,
  "verifiedType": "any",
  "minFollowers": 0,
  "maxFollowers": 0,
  "minAccountAgeDays": 0,
  "withWebsiteOnly": false,
  "activeWithinDays": 0,
  "enrichEngagement": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~x-twitter-profile-and-post-engagement-extractor/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~x-twitter-profile-and-post-engagement-extractor/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `type`, `recordType`, `status`, `message`, `username`, `name`, `text`, `createdAt`, `source`, `likeCount`, `retweetCount`, `replyCount`, `quoteCount`, `viewCount`, `bookmarkCount`, `totalEngagement`, `engagementRate`, `mediaTypes`, `isPinned`, `isHighlight`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.