Loom Transcript Scraper And Formatter

Quick Start Loom

Features

• Gets Loom transcript from URLs, useful for incorporating into your workflow automations.
• Gets extra video details like creator name, upload date, and duration.
• Supports multiple URLs.
• Returns errors if unsuccessful and which URLs it had problems with.

Headers and Descriptions for Extracted Data

• Creator: Display name of the account that uploaded the Loom.
• Title: Title of the Loom.
• Transcript: The transcript of the Loom in plain text.
• Transcript VTT: The transcript of the Loom in VTT format.
• Transcript SRT: The transcript of the Loom in SRT format.
• URL: The input URL of the Loom.
• Duration: The duration of the Loom in HH:MM:SS format.
• Duration ISO8601: The duration of the Loom in ISO8601 format.
• Upload Date: The upload date of the Loom in YYYY-MM-DD format.
• UploadDate ISO8601: The upload date of the Loom in ISO8601 format.
• Error: Any errors encountered.

Example Output

[
  {
    "url": "https://www.loom.com/share/3dd45fa63b3748cd816c8f9549febcc9",
    "transcript": "In this video, I'm going to show you how to get this actor set up and integrated into your workflows right away. So we're going to want to get the endpoint here. And we want to make sure that we get the endpoint that is here that says run actor synchronously and get data set items. Next, I'm going to copy this example input here. Now in your platform of choice, make sure you have a manual set up to send an HTTP post request to your own unique URL. And now I'm going to paste in the example input here. This actor supports multiple URLs, but for the sake of this example, I'm just going to use one URL for now. The example loom I'm going to use is this demo from loom itself here. I'm going to copy this link. I'm going to go back and I'm going to paste this in here. Now ideally, this would be a variable, but for the sake of this test, I'm just going to hard-code it. Now I'm going to run and test this step. All right, so the results came back. Let's open this up. And we'll see the URL of the loom that we transcribed. This is the entire transcript of that loom. And we'll see that there are no errors here. If there is an error, it will tell you what the error was. So for example, if you're trying to transcribe a private or you are all that's not formatted correctly, basically you'll see the error here, but error null is a good thing, which means that there is no error that came in. And then from here, we can just send this transcript into an LLM, into ChatGPT or Cloud or anything like that. Another step. And we also have the loom URL here as a reference so that way we know where the transcript came from. All right. Hope this helps. Thanks, guys.",
    "transcriptVTT": "WEBVTT\n\n00:00:02.000 --> 00:00:08.000\nIn this video, I'm going to show you how to get this actor set up and integrated into your workflows right away.\n\n00:00:08.000 --> 00:00:18.000\nSo we're going to want to get the endpoint here. And we want to make sure that we get the endpoint that is here that says run actor synchronously and get data set items.\n\n00:00:18.000 --> 00:00:30.000\nNext, I'm going to copy this example input here. Now in your platform of choice, make sure you have a manual set up to send an HTTP post request to your own unique URL.\n\n00:00:30.000 --> 00:00:40.000\nAnd now I'm going to paste in the example input here. This actor supports multiple URLs, but for the sake of this example, I'm just going to use one URL for now.\n\n00:00:40.000 --> 00:00:48.000\nThe example loom I'm going to use is this demo from loom itself here. I'm going to copy this link. I'm going to go back and I'm going to paste this in here.\n\n00:00:48.000 --> 00:00:55.000\nNow ideally, this would be a variable, but for the sake of this test, I'm just going to hard-code it. Now I'm going to run and test this step.\n\n00:00:55.000 --> 00:01:02.000\nAll right, so the results came back. Let's open this up. And we'll see the URL of the loom that we transcribed.\n\n00:01:02.000 --> 00:01:12.000\nThis is the entire transcript of that loom. And we'll see that there are no errors here. If there is an error, it will tell you what the error was.\n\n00:01:12.000 --> 00:01:25.000\nSo for example, if you're trying to transcribe a private or you are all that's not formatted correctly, basically you'll see the error here, but error null is a good thing, which means that there is no error that came in.\n\n00:01:25.000 --> 00:01:31.000\nAnd then from here, we can just send this transcript into an LLM, into ChatGPT or Cloud or anything like that.\n\n00:01:31.000 --> 00:01:38.000\nAnother step. And we also have the loom URL here as a reference so that way we know where the transcript came from.\n\n00:01:38.000 --> 00:01:40.056\nAll right. Hope this helps. Thanks, guys.",
    "transcriptSRT": "1\n00:00:02,000 --> 00:00:08,000\nIn this video, I'm going to show you how to get this actor set up and integrated into your workflows right away.\n\n2\n00:00:08,000 --> 00:00:18,000\nSo we're going to want to get the endpoint here. And we want to make sure that we get the endpoint that is here that says run actor synchronously and get data set items.\n\n3\n00:00:18,000 --> 00:00:30,000\nNext, I'm going to copy this example input here. Now in your platform of choice, make sure you have a manual set up to send an HTTP post request to your own unique URL.\n\n4\n00:00:30,000 --> 00:00:40,000\nAnd now I'm going to paste in the example input here. This actor supports multiple URLs, but for the sake of this example, I'm just going to use one URL for now.\n\n5\n00:00:40,000 --> 00:00:48,000\nThe example loom I'm going to use is this demo from loom itself here. I'm going to copy this link. I'm going to go back and I'm going to paste this in here.\n\n6\n00:00:48,000 --> 00:00:55,000\nNow ideally, this would be a variable, but for the sake of this test, I'm just going to hard-code it. Now I'm going to run and test this step.\n\n7\n00:00:55,000 --> 00:01:02,000\nAll right, so the results came back. Let's open this up. And we'll see the URL of the loom that we transcribed.\n\n8\n00:01:02,000 --> 00:01:12,000\nThis is the entire transcript of that loom. And we'll see that there are no errors here. If there is an error, it will tell you what the error was.\n\n9\n00:01:12,000 --> 00:01:25,000\nSo for example, if you're trying to transcribe a private or you are all that's not formatted correctly, basically you'll see the error here, but error null is a good thing, which means that there is no error that came in.\n\n10\n00:01:25,000 --> 00:01:31,000\nAnd then from here, we can just send this transcript into an LLM, into ChatGPT or Cloud or anything like that.\n\n11\n00:01:31,000 --> 00:01:38,000\nAnother step. And we also have the loom URL here as a reference so that way we know where the transcript came from.\n\n12\n00:01:38,000 --> 00:01:40,056\nAll right. Hope this helps. Thanks, guys.",
    "title": "Loom Transcript Grabber Overview",
    "uploadDateISO8601": "2024-12-06T14:17:58.802Z",
    "durationISO8601": "PT100.056S",
    "uploadDate": "2024-12-06",
    "duration": "00:01:40",
    "creator": "Matthew James",
    "error": null
  }
]

Usage for Workflows

Payload to add your own custom inputs when making an API call:

{
   "loomUrls":[
      {
         "url":"https://www.loom.com/share/valid-video-id"
      },
      {
         "url":"https://www.loom.com/share/invalid-video-id"
      },
      {
         "url":"https://www.example.com"
      }
   ]
}

Example of output with errors / invalid URLs

[
    {
        "url": "https://www.loom.com/share/valid-video-id",
        "transcript": "The transcript of the Loom",
        "title": "Title of the Loom.",
        "uploadDate": "2024-01-01",
        "duration": "00:01:40",
        "creator": "Creator Name",
        "error": null
    },
    {
        "url": "https://www.loom.com/share/invalid-video-id",
        "transcript": null,
        "error": "Failed to extract transcript. Check the URL."

    },
    {
        "url": "https://www.example.com",
        "transcript": null,
        "error": "Invalid Loom URL"

    }
]

Make sure to call with /run-sync-get-dataset-items so that you can use the response within the workflow.