Automation library · Documents and files

Transcribe speaker-labeled recordings with Gladia

Started by someone submitting a form, and works across Google Drive and Slack. 10 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 1Logic 4Service 5

The steps in the order they run, from what starts it.

  1. 1Receive Recording RequestForm triggerStarts it
  2. 2Configure PollingSetLogic
  3. 3Start Gladia TranscriptionHttp RequestService
  4. 4Wait For ProcessingWaitLogic
  5. 5Report Transcription FailureSlackService
  6. 6Get Transcription ResultHttp RequestService
  7. 7Route By StatusSwitchLogic
  8. 8Format Speaker TranscriptCodeLogic
  9. 9Save Transcript To DriveGoogle DriveService
  10. 10Notify Transcript ReadySlackService

How it's built

Starts on
Someone submitting a form
Steps
10, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Google Drive, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Drive and Slack accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on someone submitting a form.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 10 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 10 steps before you point it at anything that matters.