Resources · Make integration

Supadata Make integrationAutomate Supadata with Make.

Need the words spoken in a video, sitting in a sheet or a doc, without copying them by hand? The Supadata Make integration gives you 3 modules, all actions, to fetch transcripts and metadata. This page walks you through the connection and a first working scenario.

Try the Supadata integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Supadata Make integration do?

The Supadata Make integration links your Supadata account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: here, three actions that ask Supadata for a transcript, for metadata, or for any call its API accepts.

Turn videos into searchable text. A content team collects YouTube, TikTok or X links in a sheet. A module from that other app passes each link along, and Get a Transcript returns the spoken text, ready to be written back next to the link.

Give a transcript its context. Add Get Metadata after the transcript so your notes keep more than raw text. The doc gives no description of this module, so run it once and look at what it returns before you rely on it.

Reach the rest of the API. When the two ready-made modules stop short, Make an API Call sends any request Supadata's API accepts, with the same connection.

What Make does not do here: Supadata has no trigger, so nothing starts on its own from Supadata. Your scenario begins with another app or with a schedule. The same kind of app often exists in n8n too; the n8n vs Make comparison lays out both tools. To get comfortable with the editor first, see the Make training, and check Make pricing before you scale.

Connect

How do you connect Supadata to Make?

  1. 01

    Copy your API key

    Supadata needs an active account and an API key. Sign up, finish onboarding, then open your dashboard: the key is generated for you and shown there. Copy it, you will paste it into Make in a moment.

  2. 02

    Open the connection window

    In Make, add any Supadata module to your scenario and click Create a connection. A connection is your Supadata account linked to Make once, then reused by every Supadata module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several people share the workspace. Then paste the key you copied from Supadata, or follow the on-screen instructions, and save.

First scenario

Your first scenario with Supadata

GoalWhen a new video link shows up in another app, Make asks Supadata for its transcript and its metadata.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that holds your video links as the first module, since Supadata has no trigger of its own.

  2. 02

    Add Get a Transcript

    Click the + on the right of the first module, search for Supadata and choose Get a Transcript. Select your connection, then map the video from the previous module into the fields Make shows you.

  3. 03

    Chain Get Metadata

    Add Get Metadata after the transcript with another +, reuse the same connection and map the same video. Each item passing from one module to the next is called a bundle.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module's bubble to read the bundles it received, and check that the transcript text is really there before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Adjust it, then switch the scenario on.

Modules

What Supadata can do in Make

Supadata gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Supadata1

Get a Transcript

Action

In Make“Fetches a transcript of a YouTube, TikTok or X (Twitter) video.”

Hand it a YouTube, TikTok or X (Twitter) video and you get back the transcript, as text you can store, summarize or send on to the next module.

When to use it
a marketer drops competitor videos into a tracking sheet and wants the spoken script next to each link without watching them all.
Watch out
each video processed counts as one operation on your Make plan, so a long list of links adds up fast.
Supadata2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This one opens up any part of Supadata's API the two ready-made modules do not cover, sent through the connection you already set up, so no second key to manage.

When to use it
you found a Supadata feature in their API docs and neither Get a Transcript nor Get Metadata exposes it.
Watch out
you write the request yourself, so keep Supadata's documentation open for the path and the parameters.
Supadata3

Get Metadata

ActionIn the docs only

You get the metadata Supadata holds for the item you point it to, which adds context around a transcript. Make's doc gives this module no description, so treat its output as something to discover.

When to use it
after Get a Transcript, when your sheet or database needs more than the raw words.
Watch out
run the scenario with Run once and read the returned bundle before mapping any value further down.
Need help

Need help automating Supadata with Make?

A person reads every message.

FAQ

Questions about the Supadata Make integration

01Is the Supadata Make integration free?
Yes, on the Make side. Supadata is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops a run after 5 minutes, and handles files up to 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and lift the scenario cap. Supadata's own account and API key are a separate matter, handled on Supadata's side.
02What do you need to connect Supadata to Make?
An active Supadata account and its API key. After signing up and finishing onboarding, the key appears already generated in the Supadata dashboard. In Make, add a Supadata module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves Get a Transcript, Get Metadata and Make an API Call, so there is nothing to repeat when you add a second module to the same scenario.
03Does the Supadata Make integration react in real time?
No, because Supadata has no trigger module at all. Every scenario starts somewhere else: a trigger from another app, such as a new row or a new message, or the schedule on the first module. A new scenario runs every 15 minutes by default, the minimum on the Free plan; paid plans go down to 1 minute. If the app holding your video links offers an instant trigger, that app can start the scenario as soon as something happens.
04What if a Supadata module is missing in Make?
Use Make an API Call. It sends any request Supadata's API accepts, with the connection you already have, so a feature missing from Get a Transcript or Get Metadata stays within reach. You will need Supadata's documentation to write the request. Keep in mind that Make's page for this app is flagged as AI-generated from the vendor's docs and may contain mistakes; when something does not match, Supadata's own documentation is the reference to trust.
05Should you use Make or n8n for Supadata?
It depends on the tool your team already runs. The same app often has an n8n node, so the choice is less about Supadata and more about which editor you prefer to build and maintain in. On Make, you get 3 Supadata modules, including Make an API Call for anything else in the API, and a Free plan to test with 2 active scenarios. If your other automations already live in one of the two tools, staying there keeps everything in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations