Resources · Make integration

Google Cloud Speech Make integrationAutomate Google Cloud Speech with Make.

Need your recordings turned into text without copying files by hand? The Google Cloud Speech Make integration gives you 3 modules: 2 actions and 1 search. This guide shows how to link your Google Cloud project and build a first transcription flow.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Google Cloud Speech Make integration do for you?

With it, a Make scenario, the automation you build as a chain of modules, sends audio to Google's speech recognition and gets the transcript back. A module is one brick of that chain, and here you get 3 of them: two to start a recognition job and one to check on it.

Transcribe a short clip on the spot. A support team receives voice notes from customers. Start Synchronous Speech Recognition sends the clip and hands back the text once all the audio has been processed, ready to drop into a ticket.

Handle long recordings without blocking the flow. A podcast producer uploads a full episode. Start Asynchronous Speech Recognition launches the job and returns right away; Get the State of Asynchronous Speech Recognition later tells you where the job stands and gives you the result.

Feed text to the rest of your stack. Once the transcript sits in a bundle (one item passed from module to module), any other app of your scenario can store it, like the tables described in the Airtable Make integration guide.

What Make does not add: Google Cloud Speech has no trigger here, so something else has to start the scenario, and there is no Make an API Call module for this app. If you hesitate between platforms, read n8n vs Make; to learn the editor properly, see the Make training.

Connect

How do you connect Google Cloud Speech to Make?

  1. 01

    Prepare your Google Cloud project

    You need a Google Cloud account with billing enabled and the Cloud Speech-to-Text API turned on. In the Cloud Console, open APIs and Services, then Credentials, and create an OAuth client ID.

  2. 02

    Register the Make callback address

    When Google asks for the callback URI, paste https://www.integromat.com/oauth/cb/google-cloud-speech, click Create, then copy the Client ID and the Client secret shown on screen.

  3. 03

    Create the connection in Make

    Add any Google Cloud Speech module to your scenario and click Create a connection. Give it a name in Connection name if you like, then paste your credentials. That connection, your Google account linked to Make, serves all 3 modules.

First scenario

Build your first scenario with Google Cloud Speech

GoalWhen a new recording shows up in another app, Make sends it to Google Cloud Speech and fetches the transcript.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your recordings land: that module starts the flow, since Google Cloud Speech has no trigger.

  2. 02

    Add the transcription job

    Click the + on the right, search Google Cloud Speech and choose Start Asynchronous Speech Recognition. Click Create a connection if this is your first module of the app, then map the audio from the previous module.

  3. 03

    Check the job

    Add Get the State of Asynchronous Speech Recognition next and map what the previous module returned. This module reads where the job stands and gives you the result once Google has it.

  4. 04

    Test with Run once

    Click Run once, the button that runs the scenario a single time. Open the bubble above each module to read the bundles it received and check the state returned by Google.

  5. 05

    Schedule and switch on

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

Modules

What each Google Cloud Speech module does

Google Cloud Speech gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Google Cloud Speech1

Get the State of Asynchronous Speech Recognition

Action

In MakeGets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.

This one tells you whether a long transcription job has finished and hands over its result when it has. It only makes sense after the asynchronous module has launched a job.

When to use it
after a long interview or meeting recording was sent off, to pick up the text and pass it to your notes or your CRM.
Watch out
the job may still be running when this module reads it, so check the state it returns before using the text further down.
Google Cloud Speech2

Start Asynchronous Speech Recognition

Action

In MakePerforms asynchronous speech recognition: receive results via the google.longrunning.

You launch a transcription in the background and the scenario moves on without waiting for the text. Google works on the audio while your flow continues, which suits recordings too long to process in one go.

When to use it
a full webinar, a podcast episode or a long customer call that you want transcribed without holding up the scenario.
Watch out
this module does not return the transcript itself; pair it with Get the State of Asynchronous Speech Recognition to collect it.
Google Cloud Speech3

Start Synchronous Speech Recognition

Search

In MakePerforms synchronous speech recognition: receive results after all audio has been sent and processed.

Here you get the text back in the same step: Make sends the audio, Google processes all of it, and the transcript arrives as the output of the module. It is the simplest path for short clips.

When to use it
a voice message left by a customer or a short dictated note that you want as text in a ticket right away.
Watch out
Make lists it as a search, so it can return zero, one or several bundles; plan for each case in the modules that follow.
Need help

Need help automating Google Cloud Speech with Make?

A person reads every message.

FAQ

Questions people ask about Google Cloud Speech in Make

01Is the Google Cloud Speech Make integration free?
On the Make side, yes: Google Cloud Speech 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 lower the interval to 1 minute and raise execution time to 40 minutes. Google bills its own service separately: your Google Cloud account needs billing enabled, and its pricing is on the Google Cloud Speech pricing page.
02What do you need to connect Google Cloud Speech to Make?
A Google Cloud account with billing enabled and the Cloud Speech-to-Text API activated. In the Google Cloud Console, you create an OAuth client ID under APIs and Services, then Credentials, and enter the Make callback URI given in the connection steps above. Google then shows a Client ID and a Client secret. In Make, you add a Google Cloud Speech module, click Create a connection, and paste those credentials. The same connection then works for all 3 modules of the app.
03Does Google Cloud Speech trigger Make scenarios in real time?
No. The app has no trigger module at all, neither scheduled nor instant, so it cannot start a scenario by itself. The flow has to open on another app, for example the tool where your recordings arrive, or run on the schedule you set on the first module. A new scenario checks every 15 minutes by default, and paid plans let you go down to 1 minute. Google Cloud Speech modules then come after that first step.
04What if a Google Cloud Speech module is missing in Make?
It depends on what you need. The app offers 3 modules only, and unlike many other apps it has no Make an API Call module, so you cannot reach other parts of the Google API from this integration. For anything outside synchronous recognition, asynchronous recognition and job status, look for another app in Make that covers the need, or ask the Make agency team to study a custom build. Also keep in mind that the Make documentation for this app is marked as AI-generated, so verify details with Google.
05Should you use Make or n8n for Google Cloud Speech?
It depends on your criteria rather than on a winner. In Make, you get 3 ready modules for this app, a visual editor, a Free plan to start and a connection built on your own Google OAuth credentials. n8n often offers a node for the same app, so compare what each side covers for your exact case before choosing. Neither answer is universal: look at the modules you need, the way your team builds and the rest of the apps in your stack, then test the flow on the tool that fits.