Twitter (X) Screenshot Generator: MCP config, n8n workflow and API

{
  "postUrls": [
    "https://x.com/NASA/status/2107095768821576019"
  ],
  "captureMode": "postCard",
  "theme": "dark",
  "bothThemes": false,
  "includeEvidence": false,
  "fullPage": false,
  "hideReplies": true,
  "includeMetadata": false,
  "format": "png",
  "quality": 90,
  "deviceScaleFactor": "1x",
  "maxThreadHeight": 8000
}

---
name: twitter-x-screenshot-generator
description: "Screenshot capture records for public X posts and profiles, with image dimensions, format, and download link, plus the saved image files. Runs the Apify Actor nimbryxo-studio/twitter-x-screenshot-generator. Use when the user needs X (Twitter) data with fields such as type, targetUrl, profileUrl, captureMode, status, code 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/twitter-x-screenshot-generator"
  store-url: "https://apify.com/nimbryxo-studio/twitter-x-screenshot-generator"
---

# Twitter (X) Screenshot Generator

Use this skill to fetch X (Twitter) data with the Apify Actor `nimbryxo-studio/twitter-x-screenshot-generator` 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 |
| --- | --- | --- |
| `postUrls` | array | Posts to capture as clean post cards. Paste x.com or twitter.com links, bare numeric post IDs, profile links or bare usernames. Any input works in every list. |
| `captureMode` | one of `postCard`, `thread`, `profileHeader`, `fullProfilePage` | What to capture. Post links produce a single post card or a thread image; profile modes apply to profile links (and convert post links to the author profile). |
| `theme` | one of `dark`, `light`, `system` | Color theme for the screenshot. |
| `bothThemes` | boolean | When on, every target is captured twice: once in dark and once in light. Files and rows are unique per theme (one screenshot row per theme) and the run summary reports both themes. Overrides the Theme selection. |
| `includeEvidence` | boolean | Save a gzipped DOM snapshot and a JSON manifest to the key-value store for every capture, and add screenshotSha256, domSnapshotSha256, evidenceKey and manifestKey to each row. Failures still get a manifest with the typed failure state. |
| `fullPage` | boolean | When on, the whole page is captured instead of just the post card or the visible profile header. |
| `hideReplies` | boolean | Hide reply posts so screenshots stay focused on original posts. |
| `includeMetadata` | boolean | Add details to each row: post id, post URL, author handle, text snippet and the author's follower, following and post counts for posts; username, display name, follower, following and post counts for profiles. Counts are only added when X shows them. |
| `format` | one of `png`, `jpeg`, `webp` | File format of the saved screenshot. JPEG and WEBP support the quality setting; PNG is lossless. |
| `quality` | integer | Quality for JPEG and WEBP output (1-100). Ignored for PNG. |
| `deviceScaleFactor` | one of `1x`, `2x`, `3x` | Render the page at a higher pixel density for sharper screenshots. 2x doubles and 3x triples the pixel dimensions. |
| `maxThreadHeight` | integer | Maximum thread column height in CSS pixels; the saved image is DPR times taller. The value is clamped so the image cannot exceed the 32,767 px screenshot ceiling (10,922 CSS px at 3x). |

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

```json
{
  "postUrls": [
    "https://x.com/NASA/status/2107095768821576019"
  ],
  "captureMode": "postCard",
  "theme": "dark",
  "bothThemes": false,
  "includeEvidence": false,
  "fullPage": false,
  "hideReplies": true,
  "includeMetadata": false,
  "format": "png",
  "quality": 90,
  "deviceScaleFactor": "1x",
  "maxThreadHeight": 8000
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~twitter-x-screenshot-generator/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~twitter-x-screenshot-generator/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`, `targetUrl`, `profileUrl`, `captureMode`, `status`, `code`, `message`, `billable`, `accessState`, `requestedUrl`, `canonicalUrl`, `effectiveScale`, `previewLimited`, `previewLimitReason`, `thread`, `threadId`, `capturedPostCount`, `profilePostCount`, `requested`, `captured`.

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