Resources · Make integration

3Scribe Transcription Make integrationAutomate 3Scribe Transcription with Make.

Can Make send audio to 3Scribe and bring the transcript back on its own? The 3Scribe Transcription Make integration gives you 5 modules: 1 trigger, 3 actions and 1 search. This guide shows how to link your account, build a first scenario and pick the right module each time.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the 3Scribe Transcription Make integration do?

The 3Scribe Transcription Make integration links your 3Scribe account to Make so transcription work runs without copy and paste. You start jobs, spot the ones that are done and pull their text into the other tools you use, inside a scenario: the automation you build in Make, a chain of modules that runs on a schedule.

Transcripts that land where the team reads them. Watch Job Completions spots finished jobs, then Get a Transcript fetches the text so the next module can file it in a document or a message. A podcast producer gets show notes material without opening 3Scribe.

Recordings sent for transcription as they arrive. When a file shows up in another app, Create a Transcription Job starts the work in 3Scribe. A research team handing interviews over no longer has to upload each one by hand.

A quick view of the queue. List Transcription Jobs returns the jobs your account holds, one bundle per job, which helps a support lead check what is still pending before a meeting.

Be aware of the limits. Make itself warns that its documentation for this app is incomplete, because little public information exists about 3Scribe. The modules have no official description and no documented fields, so plan a test with Run once before you rely on a scenario. If something breaks, the Make troubleshooting guide helps you read the error. To learn the editor step by step, see our Make training. Weighing another tool? Our n8n vs Make comparison lays out the criteria.

Connect

How do you connect 3Scribe Transcription to Make?

  1. 01

    Add a 3Scribe module

    In your scenario, search for 3Scribe Transcription, pick any of its modules, then click Create a connection. The connection is your 3Scribe account linked to Make once, then reused by every 3Scribe module.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, which is optional but handy with several accounts. Then either approve access on the 3Scribe page that opens, or paste the key 3Scribe gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown, and Make can start listing what it reads from your 3Scribe account. If the list stays empty, recheck the key or the authorization.

First scenario

Your first scenario with 3Scribe Transcription

GoalWhen a transcription job finishes in 3Scribe, Make fetches its transcript and hands it to the next module.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Everything you build next hangs off this starting point.

  2. 02

    Place the trigger

    Search for 3Scribe Transcription, choose Watch Job Completions and select your connection. This module opens the flow each time Make finds a job that has finished.

  3. 03

    Fetch the transcript

    Click the + on the right of the trigger, add Get a Transcript and map the job coming from the trigger, so Make knows which transcript to pull.

  4. 04

    Test with Run once

    Finish a job in 3Scribe, then click Run once. Open each module's bubble to read the bundles it received, the items passed from one module to the next.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on so it keeps running without you.

Triggers

What starts a 3Scribe Transcription scenario

1 module starts a scenario when something happens in 3Scribe Transcription. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by 3Scribe Transcription as soon as it happens.

3Scribe Transcription1Watch Job Completions

Watch Job Completions

triggerIn the docs only

This trigger kicks off your scenario when transcription jobs reach the end, so the following modules only handle work that is ready to read. Make gives it no official description; going by its name, it watches for jobs that are done.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and at 15 minutes at the shortest on the Free plan.
When to use it
whenever the transcript has to go somewhere once 3Scribe is done, a shared folder, a client file or a notes app.
Watch out
run it once on a finished job before switching on, to see what the bundle actually contains.
Modules

What the 3Scribe Transcription modules can do

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

3Scribe Transcription1

Create a Transcription Job

ActionIn the docs only

Going by its name, this module hands a recording over to 3Scribe from your scenario, so transcription starts without a manual upload. It is an action: one job per bundle it receives.

When to use it
a new call recording or interview file appears in another app and should be transcribed right away.
Watch out
the documentation gives no field list, so open the module after connecting and check which inputs Make shows.
3Scribe Transcription2

Get a Transcript

ActionIn the docs only

Pulls the transcript of one job into your scenario, which means the text becomes data you can map into any next module. Pick it over List Transcription Jobs when you already know which job you want.

When to use it
right after Watch Job Completions, to turn a finished job into readable text.
Watch out
it works on one job at a time, so feed it the job from the previous module.
3Scribe Transcription3

List Transcription Jobs

SearchIn the docs only

As its name suggests, this search returns the jobs held by your 3Scribe account as a set of bundles, one per job, which gives you an overview without opening the app. Like any search, it can send back zero, one or many results.

When to use it
you need to review or report on several jobs at once rather than react to a single one.
Watch out
each returned job runs the modules after it, and each run counts as an operation on your plan.
3Scribe Transcription4

Make an API call

ActionIn the docs only

Lets you reach any endpoint of the 3Scribe API from your scenario, with the same connection, when the four other modules do not cover what you need.

When to use it
a request exists in the 3Scribe API but has no ready-made module in Make.
Watch out
you write the request yourself, so keep the 3Scribe API reference open and test it with Run once before activating anything.
Need help

Need help automating 3Scribe Transcription with Make?

A person reads every message.

FAQ

Questions about 3Scribe Transcription and Make

01Is the 3Scribe Transcription Make integration free?
Yes, on the Make side. 3Scribe Transcription is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the minimum interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your 3Scribe subscription is a separate matter that Make does not cover.
02What does it take to connect 3Scribe Transcription to Make?
A 3Scribe account and a Make account. Make's documentation lists no specific prerequisite for this app, so the generic connection steps apply: add a 3Scribe module, click Create a connection, optionally name it, then either authorize Make on the 3Scribe page or paste the key 3Scribe provides, and click Save. The connection is then shared by the 5 modules, so you only do this once per account. If the list of 3Scribe items stays empty afterwards, the key or the authorization is the first thing to check.
03Does the 3Scribe Transcription trigger react in real time?
No. Watch Job Completions is a scheduled trigger, marked with a clock badge in the editor. Make checks 3Scribe on the scenario's schedule, every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest interval allowed; paid plans can go down to 1 minute. A finished job will therefore be picked up at the next check, not the second it completes, which is fine for filing transcripts but worth knowing before promising instant delivery.
04What if a 3Scribe Transcription module is missing in Make?
Use Make an API call. It lets the scenario call any endpoint of the 3Scribe API with the connection you already have, so a request without a ready-made module is still within reach. Keep in mind that Make warns its documentation for 3Scribe is limited because little public information exists about the app, so rely on the 3Scribe API reference and test each request with Run once before switching the scenario on.
05Should 3Scribe Transcription run on Make or n8n?
It depends on your criteria rather than on a winner. On Make, 3Scribe comes with 5 modules, including a scheduled trigger and an API call module for anything else, and a visual editor where each step is tested with Run once. The same app often has an n8n node as well, so check whether it covers the jobs you need before choosing. Compare the modules available, how your team prefers to build and where your other automations already live.