Resources · Make integration

Typecast Make integrationAutomate Typecast with Make.

Need spoken audio from text that already lives in your other tools? The Typecast Make integration gives you 2 action modules, Generate a Speech and Get Voice. This page shows how to link your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Typecast Make integration do for you?

The Typecast Make integration links your Typecast account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when another app calls Make. Typecast brings two action modules to that chain, one to generate speech and one to fetch a voice.

Narrated product pages. An online store adds a product description in its catalog tool, and Generate a Speech turns that text into audio the team can attach to the listing. The data comes from a module of another app, and Typecast does the voice part.

A fixed voice for every clip. A training team wants each lesson read by the same voice. Get Voice fetches that voice first, then its details can be mapped into Generate a Speech further down the scenario.

Audio drafts for review. A marketing lead drops a script into a shared sheet, the scenario reads the row and produces a speech file, and the draft lands where reviewers already look.

Keep expectations honest: Make states it has limited documentation for Typecast, so field names and output formats are best checked in the editor with Run once. Typecast has no trigger either, so another app or a schedule has to start the scenario. If you are still choosing a platform, the n8n vs Make comparison lays out the criteria, and our Make review and Make training help you get started.

Connect

How do you connect Typecast to Make?

  1. 01

    Add a Typecast module

    In a scenario, click the + and search for Typecast. Pick Generate a Speech or Get Voice, then click Create a connection. A connection is your Typecast account linked to Make once and reused by both modules.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps later if a colleague also links an account. A label such as the workspace or the person who owns it is enough to tell them apart.

  3. 03

    Authorize and save

    Depending on what Make asks for, either approve access on the Typecast page that opens or paste the key Typecast gives you. Then click Save and the module fields become available.

First scenario

Your first scenario with Typecast and Make

GoalWhen the scenario runs, Make fetches your chosen Typecast voice and generates a speech with it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. Since Typecast has no trigger, this scenario starts on the schedule you set on its first module.

  2. 02

    Add Get Voice

    Search for Typecast, choose Get Voice and click Create a connection to link your account. Fill in the fields Make shows; once connected, Make can list what it reads from your account.

  3. 03

    Chain Generate a Speech

    Click the + on the right of Get Voice and add Generate a Speech. Map the voice details from the previous module into its fields, so each speech uses the voice you just fetched.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received, meaning the items passed from one module to the next.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the Typecast modules do

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

Typecast1

Generate a Speech

ActionIn the docs only

This is the module that gives your scenario a spoken result: it asks Typecast to create a speech, typically from text that an earlier module passed along.

When to use it
whenever a new script, description or message should end up as audio without anyone opening Typecast by hand.
Watch out
Make has not published full details for this module, so run it once and inspect the output bundle before relying on it.
Typecast2

Get Voice

ActionIn the docs only

Get Voice fetches one voice from your Typecast account, so the rest of the scenario knows exactly which voice it is working with.

When to use it
place it ahead of Generate a Speech when every clip must sound the same, and map its output into the next module.
Watch out
it only reads a voice and creates no audio, so on its own it still counts an operation without producing a file.
Need help

Need help automating Typecast with Make?

A person reads every message.

FAQ

Typecast and Make: frequent questions

01Is the Typecast Make integration free?
Yes, on the Make side. Typecast is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, at least 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 and allow unlimited active scenarios. Usage is counted in operations, one per module run on one bundle. Your Typecast account itself is a separate matter.
02What do you need to connect Typecast to Make?
A Typecast account and a Make account. The Make documentation lists no prerequisite and no official connection steps for Typecast, so you follow the generic path: add a Typecast module, click Create a connection, optionally name it, authorize Make on the Typecast page or paste the key Typecast gives you, then click Save. The same connection then serves both Generate a Speech and Get Voice, so you only do this once per account.
03Can Typecast start a Make scenario by itself?
No. Typecast has no trigger module in Make, only two actions. To run a Typecast scenario anyway, either set a schedule on the first module, which is every 15 minutes by default and can go down to 1 minute on paid plans, or begin with a trigger from another app, such as a new form entry or a new row in a sheet, and place the Typecast modules after it. Either way, test with Run once before switching the scenario on.
04What if the Typecast module you need is missing?
It depends on what you need. The integration covers only Generate a Speech and Get Voice, and Typecast has no Make an API Call module in Make, so there is no generic way to reach other parts of the Typecast service from this app. Make also says its documentation for Typecast is limited. If your case goes beyond these two modules, look for another app that covers the missing step, or ask the team for help designing the scenario.
05Should you use Make or n8n for Typecast?
It depends on your criteria rather than on a winner. In Make, Typecast gives you two action modules, no trigger and no Make an API Call module, and the scenario is built visually in the editor. The same app often exists as an n8n node too, so check the node list there against the exact actions you need. Compare which tool already hosts the rest of your automations, which one your team knows, and which modules match your use case.