Transcribe speaker-labeled recordings with Gladia, Google Drive, and Slack
Ready for 3.0What this workflow does
This workflow has 10 nodes and runs when someone submits an n8n form (“Speaker-labeled transcript”). Along the way it connects Google Drive and Slack. It also calls api.gladia.io over HTTP.
How it runs
Trigger: When someone submits an n8n form (“Speaker-labeled transcript”).
- Configure Polling (Edit Fields (Set)): sets 2 fields: wait_seconds, max_attempts
- Start Gladia Transcription (HTTP Request): calls api.gladia.io (POST)
- Wait: pauses before continuing
- Report Transcription Failure (Slack): uses Slack
- Get Transcription Result (HTTP Request): calls an HTTP API
- Route By Status (Switch): routes items into 2 branches
- Format Speaker Transcript (Code): runs custom JavaScript code
- Save Transcript To Drive (Google Drive): uses Google Drive
- Notify Transcript Ready (Slack): uses Slack
Services it uses
HTTP calls to: api.gladia.io
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- n8n Form Trigger
n8n-nodes-base.formTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Wait
n8n-nodes-base.wait - Switch
n8n-nodes-base.switch - Code
n8n-nodes-base.code - Google Drive
n8n-nodes-base.googleDrive - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow collects a public media URL via an n8n form, sends it to Gladia for diarized transcription, formats the result as a speaker-labeled Markdown note, saves it to Google Drive, and posts the Drive link (or any failure reason) to a…