Resources · Make integration

Trint Make integrationAutomate Trint with Make.

Tired of dragging every recording into Trint by hand? The Trint Make integration gives you 3 modules: one instant trigger and two actions. This guide explains each one, links your account and walks you through a first scenario you can switch on today.

Try the Trint integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Trint Make integration do for you?

The Trint Make integration links your Trint account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger or an action. With it, Make can hear when a transcript is complete or verified, send a file to Trint, or call the Trint API directly.

A handoff the moment a transcript is ready. Watch Transcript Complete/Verified starts your scenario when Trint finishes or verifies a transcript. The next module can post a message in your team chat or add a row to a tracking sheet, so an editor knows the text is waiting.

Recordings that reach Trint without a manual upload. Start the scenario from another app, such as a storage folder or a form that collects audio, then add Upload a File. Each new file goes straight into your Trint account.

Anything the listed modules leave out. Make an API Call reaches any endpoint of the Trint API with the same connection, so you are not stuck when a need falls outside the two actions.

Keep the scope in mind: the Make documentation lists no search module for Trint, so reading back existing transcripts means going through Make an API Call. Before you pick a plan, the Make pricing page sums up what each tier includes. If you are still weighing tools, n8n vs Make sets out the criteria side by side, and the Make training covers scenario building from the ground up.

Connect

How do you connect Trint to Make?

  1. 01

    Generate an API key in Trint

    You need an active Trint account. Open the account API page in Trint, click the button that creates a new API key, and copy the key right away, since it is shown during creation. A Legacy API Key also works.

  2. 02

    Add a Trint module in Make

    In your scenario, add any Trint module and click Create a connection. A connection is your Trint account linked to Make once, then reused by every Trint module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied into the connection window, or follow the on-screen instructions, then confirm. Make now lists what it can read from your Trint account inside the module settings.

First scenario

Build your first scenario with Trint

GoalWhen a new recording lands in the app where your audio is stored, Make uploads it to Trint.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that receives your recordings and its module that watches for new files.

  2. 02

    Add Upload a File

    Click the + on the right of that first module, search for Trint and choose Upload a File. Link your account with Create a connection and the API key from Trint.

  3. 03

    Map the recording

    In the Trint module, map the file coming from the previous module. A bundle is one item passed along the chain, here one audio file, so each recording becomes its own upload.

  4. 04

    Test with Run once

    Drop a sample recording in the source app, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check that the file arrived in Trint.

  5. 05

    Schedule and switch on

    If the first module runs on a schedule, open its clock to set it, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What starts a Trint scenario

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

Trint1Watch Transcript Complete/Verified

Watch Transcript Complete/Verified

Instant trigger

In Make“Triggers when the transcript is complete or verified.”

This trigger starts your scenario the moment Trint reports that a transcript is complete or verified, so the next step never waits on someone refreshing a dashboard.

How it fires
instant, the app calls Make through a webhook as soon as it happens, which is why the module shows the lightning badge.
When to use it
a newsroom or research team wants the edited text handed to the next person as soon as the transcript is signed off.
Watch out
one module covers both complete and verified transcripts, so test with Run once to see which event your account sends.
Modules

What Trint modules can do

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

Trint1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the Trint API from your scenario, reusing the connection you already made, when the two listed modules do not cover what you need.

When to use it
you want to pull back an existing transcript, which no dedicated module offers.
Watch out
you write the request yourself, so keep the Trint API reference open while you set it up.
Trint2

Upload a File

Action

In Make“Uploads a file.”

Hands a file to your Trint account straight from the scenario, so interviews and meeting recordings reach Trint without anyone opening it.

When to use it
a recording lands in shared storage or comes through a form, and you want it in Trint with no manual step.
Watch out
on the Free plan, Make handles files up to 5 MB, so check the size of your recordings before the first run.
Need help

Need help automating Trint with Make?

A person reads every message.

FAQ

Trint and Make: common questions

01Is the Trint Make integration free?
Yes, on the Make side. Trint is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. You still need your own active Trint account, which is billed by Trint, not by Make.
02What is needed to connect Trint to Make?
An active Trint account and an API key, or a Legacy API Key. Generate the key on the account API page in Trint and copy it as soon as it appears. In Make, add a Trint module, click Create a connection, give the connection a name if you like, and paste the key. For the instant trigger, click Create a webhook before creating the connection. Once saved, every Trint module in your scenarios reuses that same connection, so the setup happens only once.
03Does the Trint trigger in Make fire in real time?
Yes. Watch Transcript Complete/Verified is an instant trigger: Trint calls Make through a webhook as soon as a transcript is complete or verified, instead of Make checking on a schedule. The module shows a lightning badge in the editor to mark this. A scenario that starts from another app, like the upload example on this page, works differently: its first module runs on the schedule you set, every 15 minutes by default, or every 1 minute at the fastest on a paid plan.
04What if a Trint module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Trint API with the connection you already have, which covers needs the two actions leave out, such as reading back a transcript. The Make documentation for Trint gives no specific limit for the app, only a note that the doc is generated from Trint material and should be checked for important details. If a call fails, compare your request with the Trint API reference before anything else.
05Make or n8n for Trint?
It depends on what you need. On Make, Trint comes with an instant trigger for finished or verified transcripts, an upload action and Make an API Call, all usable from the Free plan. Many apps also have an n8n node, so check whether one exists for Trint and which actions it covers before choosing. Compare the two on the modules available for your case, how you prefer to build, and your plan limits, rather than on a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations