How to connect Google Cloud Speech-To-Text and WhatConverts
Create a New Scenario to Connect Google Cloud Speech-To-Text and WhatConverts
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Google Cloud Speech-To-Text, triggered by another scenario, or executed manually (for testing purposes). In most cases, Google Cloud Speech-To-Text or WhatConverts will be your first step. To do this, click "Choose an app," find Google Cloud Speech-To-Text or WhatConverts, and select the appropriate trigger to start the scenario.

Add the Google Cloud Speech-To-Text Node
Select the Google Cloud Speech-To-Text node from the app selection panel on the right.

Google Cloud Speech-To-Text
Configure the Google Cloud Speech-To-Text
Click on the Google Cloud Speech-To-Text node to configure it. You can modify the Google Cloud Speech-To-Text URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the WhatConverts Node
Next, click the plus (+) icon on the Google Cloud Speech-To-Text node, select WhatConverts from the list of available apps, and choose the action you need from the list of nodes within WhatConverts.

Google Cloud Speech-To-Text
⚙

WhatConverts

Authenticate WhatConverts
Now, click the WhatConverts node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your WhatConverts settings. Authentication allows you to use WhatConverts through Latenode.
Configure the Google Cloud Speech-To-Text and WhatConverts Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Google Cloud Speech-To-Text and WhatConverts Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙

WhatConverts
Trigger on Webhook
⚙
Google Cloud Speech-To-Text
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Google Cloud Speech-To-Text, WhatConverts, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Google Cloud Speech-To-Text and WhatConverts integration works as expected. Depending on your setup, data should flow between Google Cloud Speech-To-Text and WhatConverts (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Google Cloud Speech-To-Text and WhatConverts
Google Cloud Speech-To-Text + WhatConverts + Slack: Transcribes audio from Google Cloud Storage, creates a lead in WhatConverts with the transcription, and then sends a summary of the call along with a link to the WhatConverts lead in a Slack channel.
WhatConverts + Google Cloud Speech-To-Text + Google Sheets: When a new lead is registered in WhatConverts, the audio is transcribed using Google Cloud Speech-To-Text, and the transcript is added as a row to a Google Sheet for lead generation tracking.
Google Cloud Speech-To-Text and WhatConverts integration alternatives
About Google Cloud Speech-To-Text
Automate audio transcription using Google Cloud Speech-To-Text within Latenode. Convert audio files to text and use the results to populate databases, trigger alerts, or analyze customer feedback. Latenode provides visual tools to manage the flow, plus code options for custom parsing or filtering. Scale voice workflows without complex coding.
Similar apps
Related categories

About WhatConverts
Capture and analyze marketing leads in WhatConverts, then pipe data to Latenode to automate follow-ups. Qualify leads based on source & behavior using Latenode's no-code tools, triggering custom CRM updates or personalized email sequences. Scale lead management without complex coding.
Similar apps
Related categories
See how Latenode works
FAQ Google Cloud Speech-To-Text and WhatConverts
How can I connect my Google Cloud Speech-To-Text account to WhatConverts using Latenode?
To connect your Google Cloud Speech-To-Text account to WhatConverts on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google Cloud Speech-To-Text and click on "Connect".
- Authenticate your Google Cloud Speech-To-Text and WhatConverts accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I analyze call transcriptions for lead qualification?
Yes, you can. Latenode's AI blocks let you analyze Google Cloud Speech-To-Text transcriptions within WhatConverts, automatically scoring leads based on keywords and sentiment for better prioritization.
What types of tasks can I perform by integrating Google Cloud Speech-To-Text with WhatConverts?
Integrating Google Cloud Speech-To-Text with WhatConverts allows you to perform various tasks, including:
- Automatically transcribe call recordings and associate them with leads.
- Analyze call transcripts for keywords to identify high-intent prospects.
- Trigger alerts for specific phrases mentioned during customer calls.
- Update lead scores in WhatConverts based on conversation topics.
- Route calls to specific teams based on transcription analysis.
How does Latenode handle large Google Cloud Speech-To-Text transcriptions?
Latenode processes large transcriptions efficiently by using scalable cloud infrastructure, ensuring smooth performance even with extensive audio data.
Are there any limitations to the Google Cloud Speech-To-Text and WhatConverts integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- The accuracy of transcriptions depends on the audio quality of the recordings.
- Real-time transcription within WhatConverts is not supported; files must be processed.
- Complex JavaScript transformations may require advanced technical skills.