The flow
Starts it 2Model 3Logic 6Service 4
The steps in the order they run, from what starts it.
- 1When Executed by Another WorkflowExecute Workflow triggerStarts it
- 2Youtube TranscriptsTool WorkflowModel
- 3Youtube SearchTool WorkflowModel
- 4Usage ReportTool WorkflowModel
- 5OperationSwitchLogic
- 6Apify Youtube MCP ServerMcp triggerStarts it
- 7Apify Youtube SearchHttp RequestService
- 8Apify Youtube TranscriptsHttp RequestService
- 9Get Usage MetricsHttp RequestService
- 10Simplify Search ResultsSetLogic
- 11Simplify Transcript ResultsSetLogic
- 12Get Usage LimitsHttp RequestService
- 13Aggregate Search ResultsAggregateLogic
- 14Aggregate Transcript ResultsAggregateLogic
- 15Simplify Usage MetricsSetLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 15, with 1 branch
- 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. 15 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 15 steps before you point it at anything that matters.