Automation library · Content

Translate audio transcripts with Gladia and Google Drive

Started by someone submitting a form, and works across Google Drive and Google Sheets. 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. 1When Translation RequestedForm triggerStarts it
  2. 2Prepare Config ValuesSetLogic
  3. 3Start Gladia TranslationHttp RequestService
  4. 4Wait for ProcessingWaitLogic
  5. 5Log Failure in SheetsGoogle SheetsService
  6. 6Get Translation ResultHttp RequestService
  7. 7Route by StatusSwitchLogic
  8. 8Build Translation FileCodeLogic
  9. 9Save Translation to DriveGoogle DriveService
  10. 10Log Translation in SheetsGoogle SheetsService

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, Google Sheets
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Drive and Google Sheets 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.