Automation library · Integrations

Generate sound effect variation packs with ElevenLabs

Started by someone submitting a form, and works across Google Drive. 11 steps: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 5Service 5

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

  1. 1When a Brief Is SubmittedForm triggerStarts it
  2. 2Plan Takes and FolderCodeLogic
  3. 3Create Take Folder in DriveGoogle DriveService
  4. 4Build Take RequestsCodeLogic
  5. 5Explain Folder ProblemFormService
  6. 6Generate Sound EffectHttp RequestService
  7. 7Upload Take to DriveGoogle DriveService
  8. 8Record Failed TakeCodeLogic
  9. 9Record Successful TakeCodeLogic
  10. 10Build Results SummaryCodeLogic
  11. 11Show the Variation PackFormService

How it's built

Starts on
Someone submitting a form
Steps
11
Size
Medium: a working afternoon
Connects to
Google Drive
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Drive account. 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. 11 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 11 steps before you point it at anything that matters.