
loom-transcript
β 195,100by n8n-io Β· part of n8n-io/n8n
Fetch and display the full transcript from a Loom video URL. Use when the user wants to get or read a Loom transcript.
Fetch and display the full transcript from a Loom video URL. Use when the user wants to get or read a Loom transcript.
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates β shown here so you can audit it before installing. You don't need to read it to use the skill.
name: n8n:loom-transcript description: Fetch and display the full transcript from a Loom video URL. Use when the user wants to get or read a Loom transcript. argument-hint: [loom-url]
Loom Transcript Fetcher
Fetch the transcript from a Loom video using Loom's GraphQL API.
Instructions
Given the Loom URL: $ARGUMENTS
1. Extract the Video ID
Parse the Loom URL to extract the 32-character hex video ID. Supported URL formats:
https://www.loom.com/share/<video-id>https://www.loom.com/embed/<video-id>https://www.loom.com/share/<video-id>?sid=<session-id>
The video ID is the 32-character hex string after /share/ or /embed/.
2. Fetch Video Metadata
Use the WebFetch tool to POST to https://www.loom.com/graphql to get the video title and details.
Use this curl command via Bash:
curl -s 'https://www.loom.com/graphql' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'x-loom-request-source: loom_web_45a5bd4' \
-H 'apollographql-client-name: web' \
-H 'apollographql-client-version: 45a5bd4' \
-d '{
"operationName": "GetVideoSSR",
"variables": {"id": "<VIDEO_ID>", "password": null},
"query": "query GetVideoSSR($id: ID!, $password: String) { getVideo(id: $id, password: $password) { ... on RegularUserVideo { id name description createdAt owner { display_name } } } }"
}'3. Fetch the Transcript URLs
Use curl via Bash to call the GraphQL API:
curl -s 'https://www.loom.com/graphql' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'x-loom-request-source: loom_web_45a5bd4' \
-H 'apollographql-client-name: web' \
-H 'apollographql-client-version: 45a5bd4' \
-d '{
"operationName": "FetchVideoTranscript",
"variables": {"videoId": "<VIDEO_ID>", "password": null},
"query": "query FetchVideoTranscript($videoId: ID!, $password: String) { fetchVideoTranscript(videoId: $videoId, password: $password) { ... on VideoTranscriptDetails { id video_id source_url captions_source_url } ... on GenericError { message } } }"
}'Replace <VIDEO_ID> with the actual video ID extracted in step 1.
The response contains:
source_urlβ JSON transcript URLcaptions_source_urlβ VTT (WebVTT) captions URL
4. Download and Parse the Transcript
Fetch both URLs returned from step 3 (if available):
- VTT captions (
captions_source_url): Download withcurl -sL "<url>". This is a WebVTT file with timestamps and text. - JSON transcript (
source_url): Download withcurl -sL "<url>". This is a JSON file with transcript segments.
Prefer the VTT captions as the primary source since they include proper timestamps. Fall back to the JSON transcript if VTT is unavailable.
5. Present the Transcript
Format and present the full transcript to the user:
Video: [Title from metadata] Author: [Owner name] Date: [Created date]
0:00 - First transcript segment text...
0:14 - Second transcript segment text...
(continue for all segments)
Error Handling
- If the GraphQL response contains a
GenericError, report the error message to the user. - If both
source_urlandcaptions_source_urlare null/missing, tell the user that no transcript is available for this video. - If the video URL is invalid or the ID cannot be extracted, ask the user for a valid Loom URL.
Notes
- No authentication or cookies are required β Loom's transcript API is publicly accessible.
- Only English transcripts are available through this API.
- Transcripts are auto-generated and may contain minor errors.
npx skills add https://github.com/n8n-io/n8n --skill loom-transcriptRun this in your project β your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.