Instagram Transcript Scraper - Reels & Video: MCP config, n8n workflow and API

Instagram video to text: paste many reel, post or IGTV links and get each transcript with creator, caption and likes. Reads Instagram captions or uses AI speech-to-text in 29 languages, with optional timestamps per phrase. Export to JSON, CSV or Excel for subtitles and research.

Fastest route, in Claude Code:

claude mcp add --transport http instagram-transcript-scraper-reels-and-video "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/instagram-transcript-scraper-reels-and-video"

One click, signs in with Apify on first use:

Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):

npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/instagram-transcript-scraper-reels-and-video" --name instagram-transcript-scraper-reels-and-video

Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
  • MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
  • n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • example input: 5 of 5 (The schema has no required fields; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
  • code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
  • SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)

What the checks cover

What a run costs

Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.02 (the start event, $0.005 per GB, times its default 4 GB of memory), $0.004 on Business; results cost $0.50 per 1,000 results (pay per event). Checked 2026-11-12.

Results in one runStartResultsRun total
10$0.02$0.005$0.03
100$0.02$0.05$0.07
1,000$0.02$0.50$0.52

Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.

An example record

One record as the Actor's own README shows it (published by the Actor, not a run of ours; long values shortened). Your runs return records shaped like this.

{
  "status": "success",
  "postUrl": "https://www.instagram.com/p/DV29mBcMQwp/",
  "shortCode": "DV29mBcMQwp",
  "pk": "3852537424986049577",
  "id": "3852537424986049577_16278726",
  "postDescription": "Three quick tips for a calmer morning routine...",
  "thumbnailUrl": "https://scontent-iad6-1.cdninstagram.com/v/thumbnail.jpg",
  "videoUrl": "https://scontent-iad6-1.cdninstagram.com/v/video.mp4",
  "pubDate": "2025-05-11T05:12:03Z",
  "likeCount": 16799,
  "commentCount": 1159,
  "userId": "16278726",
  "userName": "sample_wellness",
  "userFullName": "Sample Wellness",
  "avatarUri": "https://scontent-iad3-1.cdninstagram.com/v/avatar.jpg",
  "fullText": "Here are three quick tips for a calmer morning routine. First, ...",
  "transcriptionMethod": "whisper",
  "createdAt": "2026-06-08T06:09:05.841Z"
}

MCP config

One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/instagram-transcript-scraper-reels-and-video. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:

Claude Code configterminal or .mcp.json

claude mcp add --transport http instagram-transcript-scraper-reels-and-video "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/instagram-transcript-scraper-reels-and-video"

Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup

Tools your agent gets

Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).

  • fetch-actor-detailsreads the input schema
  • get-actor-runchecks a run's status
  • get-dataset-itemsreads a run's results
  • get-key-value-store-recordreads a stored record such as a file or summary
  • abort-actor-runstops a run that is still going
  • dataspryva--instagram-transcript-scraper-reels-and-videoruns the Actor and returns its results

n8n workflow

A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.

Send the records to
  • Run by hand
  • Every day
  • Run Apify Actor

n8n workflowinstagram-transcript-scraper-reels-and-video.n8n.json

Actor on Apify
{
  "name": "Instagram Transcript Scraper - Reels & Video to n8n only",
  "nodes": [
    {
      "id": "1a0b1776-e55b-482b-a240-daea1acb0aa3",
      "name": "Run by hand",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "parameters": {}
    },
    {
      "id": "741112a6-53c1-46bd-a1d9-25b492e322fb",
      "name": "Every day",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        200
      ],
      "parameters": {
        "rule": {
          "interval": [
            {
              "triggerAtHour": 8
            }
          ]
        }
      },
      "notes": "Activate the workflow to run on this schedule."
    },
    {
      "id": "0741158a-d089-45b2-af66-53e316a09997",
      "name": "Run Apify Actor",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        260,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/actors/dataspryva~instagram-transcript-scraper-reels-and-video/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\n  \"videoUrls\": [\n    \"https://www.instagram.com/p/Dew5IIlNfMW/\"\n  ],\n  \"maxPosts_per_username\": 0,\n  \"transcriptionMethod\": \"auto\",\n  \"whisperModel\": \"base\",\n  \"includeSegments\": false\n}",
        "options": {
          "timeout": 310000
        }
      },
      "notes": "Actor: dataspryva/instagram-transcript-scraper-reels-and-video. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
      "notesInFlow": false
    },
    {
      "id": "5b40a6e6-40b7-405d-a086-daa0b52ab05b",
      "name": "Setup",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        0,
        -370
      ],
      "parameters": {
        "content": "## Instagram Transcript Scraper - Reels & Video\n\nSource: [dataspryva/instagram-transcript-scraper-reels-and-video](https://apify.com/dataspryva/instagram-transcript-scraper-reels-and-video) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
        "height": 340,
        "width": 460,
        "color": 6
      }
    }
  ],
  "connections": {
    "Run by hand": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Every day": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "templateCredsSetupCompleted": false
  },
  "tags": []
}

Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.

All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.

Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).

Download the long-run workflow11 of 11 checks pass, not executed

Call it from code

Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.

curl

API docs on Apify
curl -X POST "https://api.apify.com/v2/actors/dataspryva~instagram-transcript-scraper-reels-and-video/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"videoUrls":["https://www.instagram.com/p/Dew5IIlNfMW/"],"maxPosts_per_username":0,"transcriptionMethod":"auto","whisperModel":"base","includeSegments":false}'

Example input

These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.

Actor inputinput.json

{
  "videoUrls": [
    "https://www.instagram.com/p/Dew5IIlNfMW/"
  ],
  "maxPosts_per_username": 0,
  "transcriptionMethod": "auto",
  "whisperModel": "base",
  "includeSegments": false
}

FieldTypeWhat it does
videoUrls array List of Instagram video or reel URLs to transcribe. Supports /p/, /reel/, and /tv/ formats. Provide this, usernames, or both.
usernames array Usernames whose newest posts should be checked for videos. Each entry can be a username (with or without @) or a profile link such as https://www.instagram.com/natgeo/. Every video is transcribed (each video of a…
maxPosts_per_username integer How many of each username's newest posts to check (after the date and pinned-post filters below). Every video among them is transcribed (each video of a carousel on its own); a post without a video gets a record with…
transcriptionMethod string (3 options) How to extract transcripts. 'auto' tries native Instagram captions first, then falls back to Whisper AI. 'native' only uses Instagram captions. 'whisper' always uses AI speech-to-text.
whisperModel string (3 options) Whisper AI model size. Larger models are more accurate but use more memory and time. Only used when transcription method involves Whisper.
includeSegments boolean When enabled, the output will include a 'segments' array with per-segment timestamps and text alongside the full transcript. Each segment represents a distinct phrase with start/end times in seconds. Note: enabling…

4 more optional fields on the Store input tab.

What your agent receives

Each run returns a list of records. The Actor publishes 22 fields, starting with postUrl, profileUrl, shortCode, videoIndex.

FieldWhat it holdsFormat
statussuccess when a transcript was produced (an empty one counts when the video has no speech).string
postUrlLink to the post or Reelstring
profileUrlLink to the profile, on a record about a username that gave no postsstring
shortCodeThe short code in the post linkstring
videoIndexWhich video of the post this record is, counting only its videos (1 for a reel or a single video; a carousel with several videos has one record each)integer
pkInstagram's numeric id of the videostring
idInstagram's full media idstring
postDescriptionCaption of the poststring
thumbnailUrlLink to the cover imagestring
videoUrlLink to the video filestring
12 more fields
FieldWhat it holdsFormat
audioUrlLink to the audio trackstring
pubDateWhen the video was published (ISO 8601, UTC)string
likeCountNumber of likesinteger
commentCountNumber of commentsinteger
userIdNumeric id of the creatorstring
userNameUsername of the creatorstring
userFullNameDisplay name of the creatorstring
avatarUriLink to the creator's profile picturestring
fullTextThe whole transcript; empty when the video has no speechstring
transcriptionMethodnative (Instagram captions) or whisper (AI speech-to-text)string
segmentsPhrases with timestamps in seconds; only present when includeSegments is onarray
createdAtWhen the row was created (ISO 8601, UTC)string

Agent skill

A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.

SKILL.mdinstagram-transcript-scraper-reels-and-video/SKILL.md

---
name: instagram-transcript-scraper-reels-and-video
description: "Instagram video to text: paste many reel, post or IGTV links and get each transcript with creator, caption and likes. Reads Instagram captions or uses AI speech-to-text in 29 languages, with optional timestamps per phrase. Export to JSON, CSV or Excel for subtitles and research. Runs the Apify Actor dataspryva/instagram-transcript-scraper-reels-and-video. Use when the user needs Instagram data with fields such as status, postUrl, profileUrl, shortCode, videoIndex, pk 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/instagram-transcript-scraper-reels-and-video"
  store-url: "https://apify.com/dataspryva/instagram-transcript-scraper-reels-and-video"
---

# Instagram Transcript Scraper - Reels & Video

Use this skill to fetch Instagram data with the Apify Actor `dataspryva/instagram-transcript-scraper-reels-and-video` 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 |
| --- | --- | --- |
| `videoUrls` | array | List of Instagram video or reel URLs to transcribe. Supports /p/, /reel/, and /tv/ formats. Provide this, usernames, or both. |
| `usernames` | array | Usernames whose newest posts should be checked for videos. Each entry can be a username (with or without @) or a profile link such as https://www.instagram.com/natgeo/. |
| `maxPosts_per_username` | integer | How many of each username's newest posts to check (after the date and pinned-post filters below). Every video among them is transcribed (each video of a carousel on its own); a post without a video gets a record with the status not_a_video. |
| `transcriptionMethod` | one of `auto`, `native`, `whisper` | How to extract transcripts. 'auto' tries native Instagram captions first, then falls back to Whisper AI. 'native' only uses Instagram captions. 'whisper' always uses AI speech-to-text. |
| `whisperModel` | one of `tiny`, `base`, `small` | Whisper AI model size. Larger models are more accurate but use more memory and time. Only used when transcription method involves Whisper. |
| `includeSegments` | boolean | When enabled, the output will include a 'segments' array with per-segment timestamps and text alongside the full transcript. Each segment represents a distinct phrase with start/end times in seconds. |

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

```json
{
  "videoUrls": [
    "https://www.instagram.com/p/Dew5IIlNfMW/"
  ],
  "maxPosts_per_username": 0,
  "transcriptionMethod": "auto",
  "whisperModel": "base",
  "includeSegments": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~instagram-transcript-scraper-reels-and-video/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~instagram-transcript-scraper-reels-and-video/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: `status`, `postUrl`, `profileUrl`, `shortCode`, `videoIndex`, `pk`, `id`, `postDescription`, `thumbnailUrl`, `videoUrl`, `audioUrl`, `pubDate`, `likeCount`, `commentCount`, `userId`, `userName`, `userFullName`, `avatarUri`, `fullText`, `transcriptionMethod`.

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

  • Claude Code: save it as ~/.claude/skills/instagram-transcript-scraper-reels-and-video/SKILL.md, or .claude/skills/instagram-transcript-scraper-reels-and-video/SKILL.md in a project.
  • Codex and other agents: ~/.agents/skills/instagram-transcript-scraper-reels-and-video/SKILL.md, or .agents/skills/instagram-transcript-scraper-reels-and-video/ in a project.
  • Or let the skills CLI place it for your agent: npx skills add https://recipeforagents.com --skill instagram-transcript-scraper-reels-and-video
  • Set APIFY_TOKEN in the agent's environment.

Troubleshooting

Why does the client say Unauthorized or invalid token?

Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.

Source: Apify MCP server README

Why did my agent's tool list change after an update?

Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.

Source: Apify MCP server README

What happens when the agent sends input the Actor rejects?

The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.

Source: Apify MCP server README

Questions

How do I connect Instagram Transcript Scraper - Reels & Video to Claude?

In Claude Code run: claude mcp add --transport http instagram-transcript-scraper-reels-and-video "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/instagram-transcript-scraper-reels-and-video". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/instagram-transcript-scraper-reels-and-video and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.

What input does Instagram Transcript Scraper - Reels & Video need?

No field is required by the published input schema. The example on this page uses the Actor's own Store prefill, so it is a sensible first run.

What does Instagram Transcript Scraper - Reels & Video cost to run?

The Apify Store lists $0.50 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.

Which tools does the MCP config give my agent?

6 tools: fetch-actor-details, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run, dataspryva--instagram-transcript-scraper-reels-and-video. Apify's MCP server listed them for this exact URL on 2026-11-11.