The flow
Starts it 2Logic 7Service 4
The steps in the order they run, from what starts it.
- 1Test the preview pack manuallyManual triggerStarts it
- 2Refresh the reference pack weeklySchedule triggerStarts it
- 3Configure the music reference packSetLogic
- 4Validate settings and build preview queueCodeLogic
- 5Download each Music3AI previewHttp RequestService
- 6Archive preview in Google DriveGoogle DriveService
- 7Build a download failure alertCodeLogic
- 8Record the archived preview linkCodeLogic
- 9Build an upload failure alertCodeLogic
- 10Post a failure alert to SlackSlackService
- 11Collect all archived preview linksAggregateLogic
- 12Build the Slack reference pack summaryCodeLogic
- 13Post the reference pack to SlackSlackService
How it's built
- Starts on
- A clock
- Steps
- 13
- 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 a clock.
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. 13 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.
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 13 steps before you point it at anything that matters.