Twitch Live Stream, Channel & VOD Metadata Extractor: MCP config, n8n workflow and API

{
  "mode": "topStreams",
  "searchQuery": "lirik",
  "searchType": "all",
  "language": "EN",
  "streamSort": "VIEWER_COUNT",
  "videoSort": "TIME",
  "clipPeriod": "LAST_WEEK",
  "clipSort": "VIEWS_DESC",
  "includeChannelClips": true,
  "includeChannelVideos": true,
  "onlyLive": false,
  "maxItems": 3
}

---
name: twitch-live-stream-channel-and-vod-metadata
description: "Twitch records — live streams, channels, videos (VODs), clips, and games (categories) with viewers, followers, durations, thumbnails, broadcaster details, socials, schedules, and direct URLs. Runs the Apify Actor vexaloom-labs/twitch-live-stream-channel-and-vod-metadata. Use when the user needs Twitch data with fields such as recordType, title, channelName, displayName, viewersCount, viewCount 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: "vexaloom-labs/twitch-live-stream-channel-and-vod-metadata"
  store-url: "https://apify.com/vexaloom-labs/twitch-live-stream-channel-and-vod-metadata"
---

# Twitch Live Stream, Channel & VOD Metadata Extractor

Use this skill to fetch Twitch data with the Apify Actor `vexaloom-labs/twitch-live-stream-channel-and-vod-metadata` 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 |
| --- | --- | --- |
| `mode` | string, required | What to fetch. |
| `searchQuery` | string | Free-text query for `mode=search` — matches channels, categories, and videos. |
| `searchType` | one of `all`, `channel`, `game`, `video` | Restrict search results to one index. `all` returns channels, categories, and videos. |
| `channelNames` | array | Batch channel logins or channel URLs. Duplicates and the single `channelName` are merged. |
| `videoIds` | array | Batch VOD IDs or VOD URLs. Duplicates and the single `videoId` are merged. |
| `clipSlugs` | array | Batch clip slugs or clip URLs. Duplicates and the single `clipSlug` are merged. |
| `twitchUrls` | array | Channel, VOD, clip, or category URLs. Category and channel `/videos` and `/clips` tabs are supported. |
| `language` | string | Filter live streams, VODs, and clips to one broadcast language. Leave on `(any)` for no filter. |
| `streamSort` | one of `VIEWER_COUNT`, `VIEWER_COUNT_ASC`, `RECENT`, `RELEVANCE` | Sort live streams by viewers (high to low or low to high), recently started, or recommended. |
| `streamTags` | array | Only live streams carrying all of these freeform tags, e.g. `English`, `DropsEnabled`, `NoBackseating`. |
| `streamType` | one of `ARCHIVE`, `HIGHLIGHT`, `UPLOAD`, `PAST_PREMIERE`, `PREMIERE_UPLOAD` | Restrict channel or category VODs to one broadcast type. Leave blank for all types. |
| `videoSort` | one of `TIME`, `VIEWS` | Sort channel or category VODs by publish time or view count. |
| `clipPeriod` | one of `LAST_DAY`, `LAST_WEEK`, `LAST_MONTH`, `ALL_TIME` | Time window over which clips were created. |
| `clipSort` | one of `VIEWS_DESC`, `TRENDING` | Sort clips by views or trending score. |

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

```json
{
  "mode": "topStreams",
  "searchQuery": "lirik",
  "searchType": "all",
  "language": "EN",
  "streamSort": "VIEWER_COUNT",
  "videoSort": "TIME",
  "clipPeriod": "LAST_WEEK",
  "clipSort": "VIEWS_DESC",
  "includeChannelClips": true,
  "includeChannelVideos": true,
  "onlyLive": false,
  "maxItems": 3
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~twitch-live-stream-channel-and-vod-metadata/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/vexaloom-labs~twitch-live-stream-channel-and-vod-metadata/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: `recordType`, `title`, `channelName`, `displayName`, `viewersCount`, `viewCount`, `gameName`, `url`.

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