Resources · Make integration

GetTranscribe Make integrationAutomate GetTranscribe with Make.

Turn every new transcription request into a step Make handles for you. The GetTranscribe Make integration gives you 7 modules: 6 actions and 1 search. This page shows how to link your account, build a first scenario and pick the right module.

Try the GetTranscribe integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GetTranscribe Make integration do for you?

The GetTranscribe Make integration lets a Make scenario (the automation you build, a chain of steps) ask GetTranscribe for a transcription, fetch the result, and keep your folders in order. Each step is a module, one brick of the scenario, and none of it needs code.

Transcripts that start themselves. Put a module from another app first, then Create a Transcription. Whatever that first app hands over becomes a GetTranscribe job, with nobody copying files around.

Folders that follow your projects. A sales team opening a new deal, or a podcast producer starting a season, can call Create a Folder at that moment and rename it later with Update a Folder.

A reading list of past work. List Transcriptions is a search: it returns zero, one or many bundles (one item each), which the next module can pass to a spreadsheet or a chat tool.

Know the limits before you start. GetTranscribe has no trigger in Make, so a scenario starts from a schedule or from another app. Make also flags its own documentation for this app as limited, so check each module's fields in the editor after a first test. The Make pricing page explains what counts on your plan, and the n8n vs Make comparison helps if you are weighing both tools. To learn the editor itself, see the Make training.

Connect

How do you connect GetTranscribe to Make?

  1. 01

    Add a GetTranscribe module

    In a scenario, click the +, type GetTranscribe and pick any of its modules. Make then asks for a connection: your GetTranscribe account linked to Make once, and reused by every GetTranscribe module you add later.

  2. 02

    Create and name the connection

    Click Create a connection. Giving it a name is optional, yet a clear label such as the account owner helps a lot the day a teammate opens the scenario and sees several accounts listed.

  3. 03

    Authorize and save

    Follow what GetTranscribe asks for: either an authorization page where you approve Make, or a key that GetTranscribe gives you and you paste in the field. Click Save and the module is ready to fill.

First scenario

Your first scenario with GetTranscribe

GoalWhen a file shows up in another app, Make asks GetTranscribe for a transcription and then reads it back.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your files land first, since GetTranscribe has no module that can start a scenario.

  2. 02

    Add Create a Transcription

    Click the + to the right of that first module and choose Create a Transcription. Select your connection, then map what the previous module hands over (the file, for instance) into the fields Make displays.

  3. 03

    Chain Get a Transcription

    Add Get a Transcription after it. Run once first and look in the bundle from the step before for whatever identifies the new transcription: map it here so this module knows which one to fetch.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, which is the easiest way to see what GetTranscribe really sends back.

  5. 05

    Set the schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Pick your interval and turn the scenario on.

Modules

What each GetTranscribe module does in Make

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

GetTranscribe1

Create a Folder

ActionIn the docs only

You get a fresh GetTranscribe folder the moment your process needs one, instead of opening the app to make it by hand. Each run of the module spends one operation, the unit Make counts on your plan.

When to use it
a new client or project appears in your CRM and its transcripts should live in their own place from day one.
Watch out
run it once per project, or duplicate folders will pile up.
GetTranscribe2

Create a Transcription

ActionIn the docs only

This is the module that gets the work started: it sends GetTranscribe a new transcription job straight from your scenario. It is the one most GetTranscribe scenarios are built around.

When to use it
a file arrives through another app and should be transcribed without anyone uploading it again.
Watch out
the documentation lists no fields, so check what the module asks for in the editor and test with Run once.
GetTranscribe3

Get a Transcription

ActionIn the docs only

Pull one specific transcription back into Make so the next modules can use it. Pick it over List Transcriptions when you already know which item you want, typically because an earlier step just created it.

When to use it
right after Create a Transcription, to send the result to a document or a message.
Watch out
run a test to see which details come back before mapping them.
GetTranscribe4

Get a User Info

ActionIn the docs only

Read the account information of the GetTranscribe user behind your connection, so a scenario can check which account it is working with. It acts on a single item, unlike the search module.

When to use it
a team shares several connections and you want the output to show which account ran each job.
Watch out
the doc does not describe the returned details, so read them after Run once.
GetTranscribe5

List Transcriptions

SearchIn the docs only

Collect your existing transcriptions in one pass, each one coming out as its own bundle. As a search, it can return nothing, one item or many, and every following module runs once per bundle.

When to use it
you want to copy past transcripts into a sheet or review them in bulk.
Watch out
a long list means many operations downstream, so filter early.
GetTranscribe6

Make an API Call

ActionIn the docs only

Reach any endpoint of the GetTranscribe API from your scenario, with the connection you already set up. It covers what the six other modules leave out.

When to use it
you need an action from GetTranscribe that no listed module offers.
Watch out
you write the request yourself, so check whether GetTranscribe documents its API and start with a Run once test before going further.
GetTranscribe7

Update a Folder

ActionIn the docs only

Change an existing GetTranscribe folder from Make, so its setup keeps pace with the project it belongs to. It works on one folder at a time.

When to use it
a deal is renamed or closed in your CRM and the matching folder should say so too.
Watch out
the scenario needs to know which folder to touch, so check after Run once what Create a Folder sends back and keep what identifies the folder.
Need help

Need help automating GetTranscribe with Make?

A person reads every message.

FAQ

GetTranscribe and Make: common questions

01Is the GetTranscribe Make integration free?
Yes, on the Make side. GetTranscribe is a standard app, so it works on the Free plan like the 3,000+ other standard apps. The Free plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your GetTranscribe subscription is a separate matter that this page does not cover.
02What do you need to connect GetTranscribe to Make?
A GetTranscribe account and a Make account. Make's documentation lists no special prerequisite for this app. You add a GetTranscribe module, click Create a connection, optionally name it, then either approve Make on the authorization page GetTranscribe shows or paste the key GetTranscribe gives you. Click Save and every GetTranscribe module in your scenarios can reuse that same connection. If something fails, Make notes that its documentation for this app is limited, so test the connection with a single module first.
03Can a GetTranscribe scenario start on its own in Make?
Not from GetTranscribe itself. The app has no trigger module in Make, neither scheduled nor instant, so nothing inside GetTranscribe can launch a scenario. You have two ways around it. Start the scenario with a trigger from another app, for instance the tool where your files arrive. Or put a schedule on the first module: a new scenario runs every 15 minutes by default, the Free plan cannot go below 15 minutes, and paid plans go down to 1 minute. Each run then calls the GetTranscribe modules you placed after it.
04What if a GetTranscribe module you need is missing?
Use Make an API Call. It exists for GetTranscribe and lets a scenario call any endpoint of the app's API with the connection you already created. That covers actions the six other modules do not offer. Keep in mind that Make marks its documentation for GetTranscribe as limited, so you will need whatever API documentation GetTranscribe itself provides to write the request. Start small, click Run once, and read the bundle that comes back before mapping anything further.
05Should you use Make or n8n for GetTranscribe?
It depends on the tool your team already works in. On Make, GetTranscribe comes with 7 modules, including Make an API Call for anything they miss, and it runs on the Free plan. Many apps also have an n8n node, so check whether one exists for GetTranscribe and compare the actions each side lists for your use case. Neither tool is ranked here: the right choice is the one whose modules match the jobs you want to automate and whose editor your team is comfortable with.
Same platform

Other docs you might need on this stack.

Browse all integrations