Resources · Zapier integration

Deepgram Zapier integrationAutomate Deepgram with Zapier.

The Deepgram Zapier integration gives you 0 triggers, 4 actions and 0 searches. Deepgram never starts a Zap on its own: another app hands it an audio link, and Deepgram returns a transcript or a summary that the next step can store or post.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Deepgram Zapier integration actually does

It connects Deepgram, a speech AI service, to the rest of your tools through Zapier. You point one of its four actions at a public audio link coming from another app, and you get back text you can drop anywhere. Deepgram is always a step in the middle, never the starting point.

Three results come up again and again. First, a readable transcript: Create Transcription (Plain Text) returns the words as one text string, ready for a doc, a CRM note or a chat message. Second, a short digest: Create Summary condenses a long recording so a manager reads the gist instead of replaying the file. Third, long jobs handled out of band: Create Transcription (Callback) sends the audio off and asks Deepgram to deliver the result to an address you choose, once processing is done.

A fourth action, Create Deepgram API Request (Speech-To-Text), is the raw version. It returns Deepgram's full structured response rather than tidy text, which suits people who will pick through the result in later steps.

Now the limits. Zapier offers no Deepgram trigger at all, so nothing in Deepgram can kick off a Zap. There is no search either: you cannot look up an earlier transcript from a Zap. And every action wants a link to the audio, not the file itself (a recording stuck behind a login is useless here).

If you are weighing tools, the Deepgram Make integration covers the same app on Make, and the Make vs Zapier comparison lays out the general differences.

Vocabulary

Zapier words in one minute

Seven terms carry the rest of the page. Each one is explained once here.

Zap
One automation on Zapier: a starting event in some app, then the steps that follow each time. With Deepgram, it starts wherever the audio lives.
Trigger
The event in an app that starts a Zap. Once the Zap is on, Zapier sits and waits for it. Deepgram has none.
Action
What the Zap does after it starts: the step that writes, sends or creates something. All four Deepgram operations are actions.
Task
What Zapier bills you for: one action that finishes successfully. Your plan's monthly allowance is counted in tasks.
Polling vs instant
A polling trigger gets checked on a timer for new items. An instant trigger is pushed by the app the moment the event happens.
Filter
A gate placed before the Deepgram step: only files or records that match your condition get sent, so you do not spend a task on the rest.
Connection
Your Deepgram account linked to Zapier once, then reused by every step that talks to Deepgram.
Cost

What a Deepgram Zap costs in tasks

Deepgram is not a premium app, so it runs on the free plan. The catch sits elsewhere.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps only
  • BilledEach Deepgram action that succeeds
  • Not billedThe trigger, the checks, failed actions

The trigger from the other app costs nothing, however often Zapier checks it. Each Deepgram action that succeeds counts as one task, and a failed one is not counted. The free plan gives you 100 tasks a month, but only two-step Zaps: one trigger, one action. Add a Slack message after the transcript, or a filter, and you have a multi-step Zap that needs a paid plan. A few apps and actions take more than one task, so check the history after a first run.

Connect

Connect Deepgram to Zapier in three steps

  1. 01

    Open your Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens where you type the name of the tool you want to link to your Zapier account.

  2. 02

    Pick Deepgram

    Search for Deepgram, select it, then click Add connection. You need an existing Deepgram account at this point, so sign up on the Deepgram side first if you have none.

  3. 03

    Sign in and allow access

    Sign in to Deepgram in the tab that opens and grant Zapier access to the account. The connection is then saved and every Deepgram step in every Zap reuses it.

First Zap

Your first Zap: call recordings to a team channel

GoalA sales rep drops a call recording into a Google Drive folder; the transcript lands in the team's Slack channel.

  1. 01

    Start from the folder

    Create a Zap and pick Google Drive as the trigger app, then choose the folder where recordings arrive. Deepgram cannot start the Zap, so this step does.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent files of the connected account, so you map the next steps on a real recording rather than a placeholder.

  3. 03

    Keep only call files

    Add a filter on a value you saw in the test, such as the file name. Pick a text rule for text: a number rule on a name never passes.

  4. 04

    Transcribe with Deepgram

    Add Create Transcription (Plain Text), map the file's shareable link into Audio URL, and switch on Smart Format if you want punctuation and dates formatted.

  5. 05

    Post and publish

    Add the Slack step, map the transcript into the message, test each step once, then click Publish. With four steps, this Zap needs a paid plan.

Actions

The 4 Deepgram actions

Deepgram gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Transcription (Callback)

Action

In Zapier“Creates a Transcription using a Callback URL”

Hands an audio link to Deepgram and asks it to send the finished transcript to a callback address, instead of waiting inside the Zap.

When to use it
long recordings you want processed in the background, with the result picked up somewhere else.
Watch out
both the Callback URL and the Audio URL are required, so you need a working destination ready before you test.
2

Create Deepgram API Request (Speech-To-Text)

Action

In Zapier“Create a Deepgram API speech-to-text request, returning a JSON response”

Sends a speech-to-text request and returns Deepgram's complete structured response, not a single block of text.

When to use it
you plan to pull specific pieces out of the response in later steps rather than paste a transcript as is.
Watch out
the output is far less readable than the plain text action, so test it and check what came back before mapping.
3

Create Summary

Action

In Zapier“Create a summary of the content of an audio file.”

Reads a recording and writes a short summary of what was said, so nobody has to listen to the whole thing.

When to use it
a weekly meeting or a client call where the decisions matter more than every word.
Watch out
the Audio File URL must open the file directly, like a Drive web content link, a Dropbox direct media link or an S3 presigned URL.
4

Create Transcription (Plain Text)

Action

In Zapier“Creates a speech-to-text transcription from audio. Returns a text string of the transcription.”

Turns an audio file into one string of text, ready to drop into a document, a ticket or a message.

When to use it
the default pick when people will read the transcript and you want it in one piece.
Watch out
leave Smart Format off and you get raw words; turn it on for punctuation, paragraphs, dates and times.
When it breaks

When a Deepgram Zap breaks

Most failures come from the audio link or from the Zap's own design, not from Deepgram.

Zapier links one help article for this app, How to get started with Deepgram on Zapier, and documents no Deepgram rate limit. The cases below are the ones you will actually meet. For stubborn errors, the Zapier troubleshooting guide covers the general method.

  • The audio link is private

    Every action needs a publicly accessible audio URL. A file that asks for a login cannot be fetched, and the Deepgram step fails on that run.
  • Old recordings are ignored

    A Zap only reacts to files that arrive after you switch it on. The recordings already sitting in the folder need a separate job.
  • The Zap feeds itself

    If you save transcripts into the same folder your trigger watches, each new file starts the Zap again and drains your tasks fast.
  • A bulk upload is held back

    Dropping a huge batch of files at once can trip Zapier's flood protection, which holds the batch back instead of running everything.
Need help

Need help automating Deepgram with Zapier?

A person reads every message.

FAQ

Deepgram and Zapier: common questions

01Is the Deepgram Zapier integration free?
Yes, on the Zapier side. Deepgram is not a premium app, so it works on the free plan, which gives 100 tasks a month. The limit is the shape of the Zap: free Zaps have two steps only, one trigger and one action. A trigger from another app plus one Deepgram action fits. Anything more, like posting the transcript to Slack afterwards or adding a filter, turns it into a multi-step Zap and needs a paid plan. What Deepgram itself charges is not covered here.
02How many tasks does a Deepgram transcription use?
One task for each Deepgram action that succeeds. The trigger that starts the Zap costs nothing, and neither do the checks Zapier runs to look for new files. A failed action is not counted. So a Zap that transcribes a file and then posts it to a channel uses two tasks per recording, one for the transcript and one for the post. A few apps and actions take more than one task, so check the task history after your first runs.
03Does Deepgram on Zapier run in real time?
That depends entirely on the other app. Deepgram has no trigger, so the speed of your Zap is set by whatever starts it. If that trigger is instant, the app pushes the event to Zapier straight away and the plan does not matter. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. The Deepgram step then runs as soon as the trigger hands it the audio link.
04What does it take to connect Deepgram to Zapier?
An existing Deepgram account, and nothing else on the Deepgram side. In Zapier you open the Apps page, click + Add connection, pick Deepgram, sign in and grant access. The connection is then reused by every Deepgram step you add. On the audio side, the files you send must sit behind a public link, because each action fetches the recording from a URL rather than receiving the file itself. A link locked behind a login blocks every run.
05Why does Deepgram fail on a Google Drive or Dropbox file?
Almost always because the link is not public. Each Deepgram action asks for an audio URL that anyone can open, and a Drive or Dropbox link that requires a login is refused. The Create Summary field even names the right kind of link: a Web Content Link from Google Drive, a Direct Media Link from Dropbox, or a presigned URL from AWS S3. Share the file by link first, then map that link into the field.
06What if the Deepgram operation you want is not listed?
Then Zapier does not offer it for Deepgram today, and there is no hidden menu to find. The four actions cover plain text transcripts, summaries, callback jobs and the raw speech-to-text response. The raw request returns Deepgram's full structured answer, so a value missing from the plain text action can sometimes be picked out of it in a later step. If that still falls short, the job needs a different route than this integration, outside these four actions.
07Zapier, Make or n8n for Deepgram?
Judge it on criteria, not on a ranking. On Zapier, Deepgram offers four actions and no trigger, so another app always starts the flow. The free plan stops at two steps, which covers trigger plus transcript but not a follow-up step. Every successful action costs a task. Check those three points against your volume of recordings and the number of steps your flow needs, then compare with what the other tools offer for the same app.