Zapier Integration — transcription without a single line of code

What you can build

• "Slack message in #meetings as soon as a Zoom meeting transcription is ready."
• "New audio file in Google Drive → upload and transcribe automatically."
• "Create a Notion page with the transcript of a podcast episode as soon as I drop it in Dropbox."
• "Email my team with the SRT download link once a YouTube upload has been transcribed."
• "When the DeepScript balance drops below €5 → auto top-up via the Stripe customer portal link."

Code samples

# Zap: Auto-transcribe meeting recordings from Drive
trigger:
  app: google-drive
  event: New File in Folder
  folder: /Meetings/Recordings

action_1:
  app: deepscript
  action: Upload Audio for Transcription
  inputs:
    file: {{trigger.file}}
    model: premium
    language: de

action_2:
  app: deepscript
  action: Get Transcript Text
  inputs:
    transcriptionId: {{action_1.id}}
    waitForCompletion: true   # Zapier polls until done

action_3:
  app: slack
  action: Send Channel Message
  inputs:
    channel: "#meetings"
    text: |
      Transcript ready: {{trigger.file.name}}
      Duration: {{action_2.duration}}s
      Speakers: {{action_2.speakerCount}}
      First 200 chars: {{action_2.text | truncate: 200}}

{
  "app": "deepscript",
  "auth": {
    "type": "api_key",
    "header": "X-API-KEY",
    "value": "ds_live_xxx"
  },
  "test": {
    "endpoint": "https://api.deepscript.com/v1/account/profile",
    "method": "GET"
  }
}

Setup in a few steps

1. 1

   Connect the DeepScript app in Zapier

   In the Zapier editor under "Apps", search for "DeepScript" and click "Connect". Paste the API key from the DeepScript dashboard — Zapier hits `/v1/account/profile` once to validate the key.

2. 2

   Pick a trigger

   Either use a DeepScript event (`New Transcription Completed`, `Balance Low`) as the trigger, or start from another app event (e.g. Drive file, Calendly meeting) and use DeepScript as an action.

3. 3

   Stitch actions together

   `Upload Audio for Transcription` needs a file URL or stream from a previous step. Model (standard/premium) and language (auto or ISO 639-1) are dropdowns. Optional: a wait-for-completion toggle so downstream steps receive the finished transcript.

4. 4

   Turn the Zap on and monitor

   Turn on the Zap, send a test audio through, and check the Zapier History tab. On errors (HTTP 4xx/5xx) Zapier shows the DeepScript RFC 7807 error response directly.

Frequently asked questions