Resources · Make integration

Temi Make integrationAutomate Temi with Make.

What can Make do with your Temi transcript jobs? The Temi Make integration gives you 8 modules: 1 scheduled trigger, 6 actions and 1 search. This page shows how to link your account, build a first scenario and pick the right module for each job.

Try the Temi integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Temi Make integration let you automate?

The Temi Make integration links your Temi account to Make, a visual tool where you chain apps without writing code. You build a scenario (the automation itself), made of modules (one brick each: a trigger, an action or a search), and Make runs it for you on the jobs in your Temi account.

Transcripts that land where your team works. Start with Watch Job Events, add Get a Transcript, then drop the text into the document, sheet or inbox of another app. Nobody has to open Temi to copy and paste.

A review link for the person who needs to check the text. Share a Transcript Editor URL produces a link to the Temi editor, which you can post in a chat message or a task so a colleague corrects the transcript on the spot.

New jobs sent from your other tools. Create a Job opens a job in Temi from inside a scenario, and Get a Job Status tells you where it stands. Search Jobs and Delete a Job help keep the account tidy.

If a module is missing, Make an API Call reaches the rest of the Temi API with the same connection. One caution: Make labels its Temi documentation as AI-generated, so check important details with Temi. If you also look at n8n, the n8n vs Make comparison sets the criteria side by side, and the Make training covers the editor from zero.

Connect

How do you connect Temi to Make?

  1. 01

    Copy your Temi API key

    Log in to Temi, open your account settings and go to the developer section. The API key is displayed on screen: copy it. You need an active Temi account for this, so create one first if you do not have it.

  2. 02

    Add a Temi module in Make

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

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like (this field is optional), paste the API key you copied, then follow the instructions on screen. Make now lists what it can read from your account.

First scenario

Your first scenario with Temi

GoalWhen a job event appears in Temi, Make fetches the matching transcript so you can pass it to another app.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.

  2. 02

    Set up the trigger

    Search for Temi, pick Watch Job Events and choose your connection, or click Create a connection if this is your first Temi module.

  3. 03

    Add Get a Transcript

    Click the + to the right of the trigger, pick Get a Transcript and map the job from the trigger, so each event leads to its own transcript.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles (the items passed from one module to the next) that each module received.

  5. 05

    Schedule and switch on

    On the first module, open Scheduling: a new scenario checks every 15 minutes by default. Keep it or change it, then switch the scenario on.

Triggers

What starts a Temi scenario

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

Temi1Watch Job Events

Watch Job Events

triggerIn the docs only

Watch Job Events is the only trigger in the Temi app: it picks up events on your Temi jobs and hands each one to the rest of your scenario as a bundle, so the next modules know which job to work on.

How it fires
it is a scheduled trigger, meaning Make checks Temi on the scenario's schedule (every 15 minutes by default, at least 15 minutes apart on the Free plan).
When to use it
as the first module whenever a Temi job should set off work elsewhere, such as fetching a transcript or sharing an editor link.
Watch out
Make lists the module without a description, so run it once and read the bundle before you map anything.
Modules

What the Temi modules do

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

Temi1

Create a Job

ActionIn the docs only

Create a Job opens a new job in your Temi account straight from a scenario, which spares you a trip to the Temi interface each time a file comes in from another tool.

When to use it
after a module from another app has produced something you want transcribed.
Watch out
the doc gives no field list, so fill it once, click Run once and check the job in Temi.
Temi2

Delete a Job

ActionIn the docs only

Delete a Job removes one job from your Temi account, which is handy for clearing out work you no longer need once its result is stored somewhere else.

When to use it
at the very end of a scenario, after the transcript has been copied to its final place.
Watch out
treat the deletion as permanent and test it on a throwaway job first.
Temi3

Get a Job Status

ActionIn the docs only

Get a Job Status reads where a given Temi job stands, so your scenario can decide what to do next instead of guessing whether the work is done.

When to use it
right after Create a Job, or before Get a Transcript when you are not sure the job is ready.
Watch out
each check counts as one operation, the unit Make deducts from your plan.
Temi4

Get a Transcript

ActionIn the docs only

Get a Transcript pulls the text of one Temi job into your scenario, where the following modules can save it, send it or pass it to another app.

When to use it
after Watch Job Events or Get a Job Status has pointed to a job you care about.
Watch out
it works on one job at a time; to handle several, start from Search Jobs, which returns one bundle per job.
Temi5

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the Temi API with the connection you already set up, for the cases the seven named modules do not cover.

When to use it
when you need a Temi feature that has no module of its own in Make.
Watch out
you have to know the endpoint yourself, so keep the Temi API reference open while you fill it in.
Temi6

Search Jobs

SearchIn the docs only

Search Jobs looks through the jobs in your Temi account and returns what it finds, zero, one or several items, each as its own bundle for the modules that follow.

When to use it
when you have to act on a set of jobs rather than a single one, for a cleanup or a report.
Watch out
every returned bundle runs the next modules again, and each run counts as operations.
Temi7

Share a Transcript Editor URL

ActionIn the docs only

Share a Transcript Editor URL gives you a link to the Temi editor for one transcript, so another person can open it and correct the text without you forwarding files.

When to use it
when a colleague or a client has to review a transcript before it goes out.
Watch out
post the link only where the right people can see it, since it opens the transcript itself.
Need help

Need help automating Temi with Make?

A person reads every message.

FAQ

Temi and Make: common questions

01Is the Temi Make integration free?
Yes, on the Make side. Temi is a standard app, so it is 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. Paid plans (Core, Pro, Teams and Enterprise) go down to 1 minute between runs and count usage in credits. Your Temi subscription is separate: check the Temi pricing page for it.
02What do you need to connect Temi to Make?
You need an active Temi account and its API key. In Temi, open the account settings, go to the developer section and copy the key shown there. In Make, add any Temi module, click Create a connection, optionally name it, and paste the key. The same connection then serves all 8 Temi modules, including Make an API Call, so you only do this once per account. No webhook step is needed either: Make asks for one only with instant modules, and Temi has none.
03Does the Temi trigger in Make fire instantly?
No. Watch Job Events is a scheduled trigger: Make checks Temi on the scenario's schedule instead of being called by Temi the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest gap allowed, while paid plans can go down to 1 minute. If you need tighter timing, shorten the schedule on a paid plan. For a first test, Run once lets you check the trigger's output without waiting for the schedule.
04What if a Temi module is missing in Make?
Use Make an API Call. It calls any endpoint of the Temi API with the connection you already have, which covers what the other 7 modules leave out. Keep in mind that Make marks its Temi documentation as AI-generated and possibly inaccurate, so confirm the details of an endpoint with Temi before building a scenario that depends on it. If no endpoint fits either, send the data to another app that handles the step instead.
05Should you use Make or n8n for Temi?
It depends on what your team already runs. On Make, Temi comes with 8 ready modules, a scheduled trigger and Make an API Call for everything else, all set up through a visual editor. Many apps also have an n8n node, so check whether Temi has one before deciding. Then compare on the criteria that matter to you: the modules you actually need and the tool your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations