A Deepgram connection lets the Deepgram steps transcribe recordings — calls, voice notes, meetings — and make speech with Deepgram's voices, using your company's own Deepgram account. Bizomate does not pay for or resell AI use: Deepgram bills your project, and each run's output shows what it used.

Who can do this

Workspace Admins and Editors, on every plan — Deepgram is not a premium connection. Viewers see the connection but cannot add or change it.

On Deepgram's side, someone who can create keys in the Deepgram project.

Steps

In Deepgram, make the key:

  1. Sign in at console.deepgram.com and open the project to bill — Deepgram makes one when you sign up.
  2. Open API Keys and select Create a New API Key.
  3. Name it — for example Bizomate — and keep the Member role. Choose Never for expiry, or a date (and set the same date in Bizomate).
  4. Copy the key. Deepgram shows it only once.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under AI, select Deepgram. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace Deepgram.
  4. Paste the key in API key. "Stored encrypted. It is never shown again after you save."
  5. Optional: if the key has an end date, choose it in This key expires on · optional.
  6. Leave Test the connection before saving ticked. Bizomate reads the key's project before keeping it.
  7. Select Save connection. The button reads Testing, then the dialog closes.

The toast "Connection added" says "“Consulace Deepgram” is ready. Every workflow in this workspace can use it."

What happens next

  • Test in the connection's panel answers with the project's name — Reached Deepgram · project Consulace (or how many projects, when the key reaches several). It costs nothing.
  • In the designer, the Deepgram steps list it under Connection: Transcribe audio and Text to speech.

Good to know

  • To use a new key: open the connection's panel and select Replace key, paste the new key and select Replace key. The old one is used until then. With Test the connection before saving ticked, nothing changes if Deepgram refuses it. The toast says "Key replaced".
  • Usage and balance are on the project's Usage and Billing pages in Deepgram.

If something goes wrong

What you see Why What to do
"Fill in API key." The box is empty. Paste the key.
Deepgram refused it — "Deepgram refused: … Check the connection's details on Connections. Nothing was saved." The key is wrong, deleted or expired. Make a new key in Deepgram and paste the whole of it.
"Deepgram refused the API key. Replace it on Connections." (in a run) The key was deleted or expired. Make a new key and replace it.
"Deepgram says too many requests, or the account is out of credit. Set this step to try again, or check the account." Too many at once, or the project's balance is used up. Check billing in Deepgram, or set the step's If this step fails to try again.
"Could not reach Deepgram: …" or "Deepgram did not answer in time." Deepgram could not be reached, or was slow. Try again in a few minutes.