The flow
Starts it 1Service 15
The steps in the order they run, from what starts it.
- 1Text to SpeechHttp Request ToolService
- 2Text to Speech with TimestampsHttp Request ToolService
- 3Stream Text to SpeechHttp Request ToolService
- 4Stream Text to Speech with TimestampsHttp Request ToolService
- 5Create TranscriptHttp Request ToolService
- 6Voice ChangerHttp Request ToolService
- 7Create Sound EffectHttp Request ToolService
- 8Audio IsolationHttp Request ToolService
- 9Voice DesignHttp Request ToolService
- 10Save Voice PreviewHttp Request ToolService
- 11List VoicesHttp Request ToolService
- 12Get VoiceHttp Request ToolService
- 13Delete VoiceHttp Request ToolService
- 14Edit VoiceHttp Request ToolService
- 15List Similar VoicesHttp Request ToolService
- 16Elevenlabs API MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 16
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
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. 16 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 itNothing 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 16 steps before you point it at anything that matters.