Google Cloud Dialogflow

Google Cloud Dialogflow is an API — you call it from whatever you build, on any platform with an HTTP client.

There is nothing to install — Google Cloud Dialogflow is used in the browser. Create an account on the vendor's site and upload or connect your audio.

Google-cloud-leaning; pricing complex; ecosystem-tied.

Developers building voice and chat agents on Google Cloud with deep Google ecosystem integrations.

No. Google Cloud Dialogflow is a proprietary API. If you need source you can read and run yourself, the open-source tools in this directory are the place to look.

In this directory Google Cloud Dialogflow is filed under meetings, agents, api as a API.

There is a side-by-side page at /tools/googlecloud-dialogflow-alternatives comparing Google Cloud Dialogflow with the closest tools in the same category on price, platform and features.

Yes. If what you want is transcripts rather than the tool itself, Whipscribe does the same job as a hosted API: submit a file or URL, poll a job id, pull the result as txt, json, srt, vtt or docx. $0.012 a minute — about $0.72 an audio hour — bought as credits that never expire. The automation recipes on this site show it wired to Drive folders, Zoom recordings, S3 buckets and no-code platforms.

Google Cloud Dialogflow is another vendor's product; Whipscribe is a per-minute transcription service. Recordings are transcribed on our own servers and never used for training, and every job returns five formats plus an AI summary, quotes and topics. The first 20 minutes of any recording are transcribed free, and a pack from $6 (500 minutes) transcribes the rest and opens every export.

$0.012 a minute — about $0.72 an audio hour — bought as credits that never expire. There is no subscription and no monthly minimum: a 3-hour recording is about $2.16, a thousand-hour archive is about $720 once. The first 20 minutes of any recording are transcribed free, and a pack from $6 (500 minutes) transcribes the rest and opens every export, so you can see what your recording holds before paying anything.

Three things are moving across the whole speech-to-text market right now: summaries, action items and speaker insights generated on top of the transcript rather than sold separately; private, secured deployment where the audio never leaves a boundary you control; and agent access — transcription exposed as a tool that Claude, Cursor or a workflow runner can call directly. Whipscribe ships all three today: per-job insights, our own servers, and an MCP server.