Snapchat Publisher & Show Episode Finder: MCP config, n8n workflow and API

{
  "mode": "byPublisher",
  "publisherUrlsOrIds": [
    "efd8a13d-b69a-41d0-9c04-d19f87829798"
  ],
  "country": "US",
  "locale": "en-US",
  "includeStories": false,
  "includeShowSeasons": false,
  "includeSpotlights": false,
  "includeEpisodeMedia": false,
  "maxEpisodesPerPublisher": 3,
  "maxItems": 1
}

---
name: snapchat-publisher-and-show-episode-finder
description: "Snapchat publisher and Snap Show profiles with subscriber counts, full season and episode catalogues, HLS media, Spotlight cards and Discover feed stories. Runs the Apify Actor dataspryva/snapchat-publisher-and-show-episode-finder. Use when the user needs Snapchat data with fields such as recordType, publisherId, pageUrl, displayName, username, isVerified 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: "dataspryva/snapchat-publisher-and-show-episode-finder"
  store-url: "https://apify.com/dataspryva/snapchat-publisher-and-show-episode-finder"
---

# Snapchat Publisher & Show Episode Finder

Use this skill to fetch Snapchat data with the Apify Actor `dataspryva/snapchat-publisher-and-show-episode-finder` 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` | one of `byPublisher`, `byEpisodeUrl`, `discover`, required | What to collect: publisher catalogues, individual episodes, or the current Discover feed. |
| `publisherUrlsOrIds` | array | (mode=byPublisher) Publisher or show page URLs, story.snapchat.com/p/{id} links, or bare businessProfileId UUIDs. |
| `country` | string | Country context for episode requests and the Discover feed. |
| `locale` | string | (mode=discover) Language-region tag such as en-US, en-GB or de-DE. Invalid values fall back to en-US. |
| `includeStories` | boolean | (mode=byPublisher) Walk every season and return every publicly listed episode in episodes[]. The page's latest stories stay in premiumStories[] for compatibility. |
| `includeShowSeasons` | boolean | (mode=byPublisher) Include premiumShowSeasons[] with season IDs, numbers and declared episode counts. |
| `includeSpotlights` | boolean | (mode=byPublisher) Include publisherSpotlights[] with media URLs, creator info and engagement stats. |
| `includeEpisodeMedia` | boolean | (mode=byPublisher) Fetch episode-level HLS video tracks and snap media for each returned episode. Adds extra requests per episode. |
| `maxEpisodesPerPublisher` | integer | (mode=byPublisher) Hard cap on episodes[] per publisher. |
| `maxItems` | integer | Hard cap on dataset rows across all modes, including error rows. |

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

```json
{
  "mode": "byPublisher",
  "publisherUrlsOrIds": [
    "efd8a13d-b69a-41d0-9c04-d19f87829798"
  ],
  "country": "US",
  "locale": "en-US",
  "includeStories": false,
  "includeShowSeasons": false,
  "includeSpotlights": false,
  "includeEpisodeMedia": false,
  "maxEpisodesPerPublisher": 3,
  "maxItems": 1
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~snapchat-publisher-and-show-episode-finder/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/dataspryva~snapchat-publisher-and-show-episode-finder/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`, `publisherId`, `pageUrl`, `displayName`, `username`, `isVerified`, `subscriberCount`, `bio`, `profilePictureUrl`, `squareHeroImageUrl`, `snapcodeImageUrl`, `websiteUrl`, `category`, `subcategory`, `publisherType`, `primaryColor`, `hostUserId`, `address`, `mutableName`, `shouldHideUsername`.

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